Backing Up a Homelab as Code: Docker Configs to a Private Git Repo, Without Leaking Secrets

Tue, 04 Aug 2026 00:00:00 +0000

If my main Docker host died tomorrow, how fast could I rebuild it? For a long time the honest answer was “slowly, and from memory.” The fix is to treat the box’s configuration as code: every docker-compose.yml, Dockerfile, and config file committed to a private git repo, so reimaging is a git clone and a handful of docker compose up commands.

The trap is that a live Docker tree is a minefield of secrets — .env files, TLS private keys, API tokens hardcoded into compose files — and pushing any of them to GitHub, even a private repo, is a bell you can’t fully un-ring. This post is the repeatable procedure I landed on: what to commit, what to never commit, and the automated checks that keep the second category out.

Disaster-Recovery on Linux Colorado

Backing Up a Homelab as Code: Docker Configs to a Private Git Repo, Without Leaking Secrets