Dev House self-hosted infrastructure
Three servers run every Dev House website, app and automation: managed in one place, with auto-renewed HTTPS and configuration backed up to Git every night.
Results
- 3serversmanaged in one place
- 00:00every nightconfiguration to Git
- 100%sites on HTTPSauto-renewed certificates
The problem to solve
Many services spread over three machines, each set up differently; after an incident it was hard to know the right configuration or rebuild it.
How we solved it
Everything moved to Docker Compose, managed with Portainer and Cockpit; Nginx in front with auto-renewed Let's Encrypt certificates; every night a script collects each service's configuration (secrets stripped, only variable names kept) and pushes it to Git; fail2ban blocks SSH password guessing.
Project overview
A system Dev House built for itself and runs every day. The numbers below are its real configuration.
Three servers run every Dev House website, app and automation: managed in one place, with auto-renewed HTTPS and configuration backed up to Git every night.
• One place to see and control every container on three machines • Configuration has a daily history and can be rebuilt from Git • No secrets in the repository, only variable names • Certificates renew themselves; password guessing is blocked
Main features
Central management
Portainer and Cockpit across all three servers.
Configuration backup
To Git every night at 00:00, with a service map.
Automatic HTTPS
Let's Encrypt certificates renew for every domain.
Related services
Technology used
Want a website like this?
Tell us what you need and we will suggest the right package.