$ cat project.md
compose-homelab-starter
An opinionated docker-compose starter for a self-hosted homelab: reverse proxy, monitoring, backups.
Batteries-included Compose stack: Caddy, Grafana, Prometheus, and a backup sidecar that actually tests restores.
The problem
A small, annoying task that was eating time and attention every week. We measured it before touching anything.
The approach
One focused change, reproducible, with a guardrail and an obvious way to turn it off. No magic, no vibes.
$ ./run --dry-run
[ ok ] plan looks sane
$ ./run --applyThe receipts
Before/after benchmarks, the failure modes we hit, and the tradeoffs we accepted. The repo has the full runbook.
Convinced? The repo is one command away.
git clone$ related lab notes
# lab note
Don’t give the homelab agent root: build a CI/CD control plane instead
An AI agent can draft infrastructure changes, but it should not hold a root SSH key to the hypervisor. This pattern puts proposed changes through protected CI/CD, least-privilege credentials, telemetry, and tested rollback paths.
# lab note
Homelab Mythbusters: do you really need Kubernetes?
We ran the same workload on Compose and k3s for a month and measured everything.