Production infrastructure & self-hosting
A production-style deployment of GitHub Readme Stats, hardened behind Nginx with TLS and hosted on Oracle Cloud.
A real-world self-hosting project used to demonstrate the complete path from an application container to a publicly accessible production service.
The goal was to run GitHub Readme Stats under personal infrastructure while making the service reproducible, externally reachable and protected by a proper reverse-proxy and TLS setup.
The service is containerized and placed behind Nginx. Nginx provides the public HTTP boundary while the application remains isolated behind the reverse proxy.
The deployment separates application execution from public traffic handling, creating a foundation that can be extended with additional services later.
The upstream application needed to run consistently across development and deployment environments.
Package the service as a Docker workload.
Containerization makes the runtime reproducible and isolates application dependencies from the host.
The application should not directly own the public HTTP boundary.
Place Nginx in front of the application.
A reverse proxy creates a clear boundary for routing, TLS termination and future service expansion.
The project was built around the practical sequence of containerization, host configuration, reverse proxy setup, DNS and HTTPS rather than treating deployment as an afterthought.
The project demonstrates the ability to reason about the complete deployment path rather than stopping at a locally working application.
Public traffic terminates at the reverse-proxy layer with TLS. The application is kept behind the proxy instead of being exposed directly.
Self-hosted production-style environment
TLS-protected external service
Containerized application behind reverse proxy
