Project · Ongoing
Homelab & Self-Hosting
Own infrastructure, from the network to the container
Maintaining a personal infrastructure with several services, two hosts and controlled internet exposure, without depending on a single machine.
The problem
A homelab grows quickly: containers, certificates, access and services that cannot be left open to anyone. The infrastructure has to be understandable, secure and maintainable with the time available.
The infrastructure
- Two active hosts: a home server running Proxmox and an Oracle Cloud VPS.
- About 20 Docker services.
- SWAG as reverse proxy and certificate manager.
- Authelia for authentication.
- CrowdSec for perimeter protection.
- Portainer/Dockhand for centralised management.
- Uptime Kuma for monitoring.
Decisions
- Split services between the home host and the VPS.
- Expose only what is necessary through SWAG, with managed certificates.
- Put Authelia in front of the services that need it.
- Add CrowdSec as a perimeter protection layer.
- Centralise operations and monitor for outages.
Outcome
An infrastructure in continuous use, with about 20 services and regular maintenance. No availability metrics or network details are published.