$ whoami

First post laid out the stack in one sentence. This one walks the whole thing. One host, two platforms Everything sits on a single Proxmox host (currently a laptop - real hardware later). Docker Compose handles the simple services - one folder each, reverse-proxied through Caddy with Let’s Encrypt TLS via Cloudflare DNS-01. Things that just need to run and stay running. k3s is the platform I’m betting on long-term - same TLS via cert-manager, state in Git, Argo CD reconciling via app-of-apps so the whole cluster comes from one path. ...

First post, so: why this blog exists. I run a small homelab - one Proxmox host running the services I actually use, and a place to practise tools I want to get good at. The infrastructure lives in Git; the reasoning lives here. Writing forces the lesson to stick: if I can’t explain why I chose something, I didn’t understand it well enough to choose it. The stack, in the order I’ll cover it: Proxmox, Docker Compose for the simple stuff, k3s as the platform I’m betting on, Argo CD for GitOps, Terraform for DNS, Tailscale holding it together. Posts lean practical - how I set it up, why, and what broke. Less tutorial, more “here’s the thing nobody told me.” ...