Nº 06 — Self-hosted infrastructure
VPS & services
The server behind this site: a shared reverse proxy, containerized services, nightly backups, and deploys driven entirely by GitHub Actions.
Nº 06 — Diagram
- Year
- 2026
- Role
- Administration and automation
- Stack
- CaddyDocker ComposeGitHub ActionsUmamiUptime Kuma
01Context
Several sites, a few monitoring services, one small server: everything had to be versioned, replayable, and a rollback should never require rebuilding anything.
02What I built
- A shared reverse proxy: each project versions its own configuration, validated in CI before it reaches the server.
- Cookie-free audience measurement, plus availability and resource monitoring.
- Automatic nightly backups, stored off the server.
- Deploys triggered by a merge, with no manual step.
03Technical decisions
- All configuration lives in the repository: the server only holds what a deploy copied there.
- Images are pinned to a version: an upgrade goes through a pull request, like code.
- Secrets are generated on the server and never leave it.