Every time you spin up a new VPS for a side project or a client, you run into the same tedious cycle: configuring Nginx, setting up Let's Encrypt certificates, opening ports, and ensuring containers stay updated.
If you mess up one line in your Nginx configuration, your SSL drops. If you forget to update your images, you miss critical security patches.
Here is the exact architecture I use to deploy apps in production in under 2 minutes, completely automated.
The Holy Trinity of Docker Architecture
To achieve hands-off operations, you need three elements working in perfect harmony:
- The Reverse Proxy (Nginx): Routes traffic from port 80/443 to the correct container dynamically.
- The SSL Companion: Automatically requests and renews Let's Encrypt certificates based on environment variables.
- The Automator (Watchtower): Scans your running containers daily, pulls new base images, and restarts them gracefully without downtime.
How it works in practice
Instead of writing complex configuration files for every new app, you just add three simple environment variables to any new container you launch:
VIRTUAL_HOST=yourdomain.comLETSENCRYPT_HOST=yourdomain.comLETSENCRYPT_EMAIL=admin@yourdomain.com
The proxy detects the new container, handles the routing, fetches the SSL certificate, and Watchtower keeps it updated. Total maintenance required: Zero.
Get the Battle-Tested, Production-Ready Files
If you want to skip the trial-and-error of configuring network permissions, volume mappings, and cron backup scripts from scratch, I have packaged the entire stack into a clean, drop-in template.
It includes the complete docker-compose.yml, optimized security headers, and a quick-start guide to get your server running securely in 60 seconds.
👉 Download the Production-Ready Docker Stack Here
How are you currently managing SSL and reverse proxies for your indie projects? Let me know in the comments!
Top comments (0)