Turn a Hand-Built Proxmox Cluster Into Code Without Breaking It
IaC guides assume an empty account. Here's the import-first approach for a Proxmox homelab already running things you cannot afford to lose.
Turn a used mini PC into your own private cloud — stream your movie library, automate your home, block ads on every device, keep your photos off Big Tech, and run your own ChatGPT-style AI from one quiet shelf. Every guide here was built on a live cluster, and every one tells you what broke on the way.
The Start Here roadmap remembers which steps you've finished.
Four HP EliteDesk 705 G4 mini PCs stacked flat and running Proxmox VE, cabled to an 8-port gigabit switch, with a 4-bay NAS for backup storage and a tower UPS protecting everything from power loss. Total idle power draw: ~55W.
Bring running Proxmox containers under OpenTofu without restarting one: import blocks, the generated-config cleanup, and a clean plan that becomes your drift detector.
I built a read-only simulator that answers whether a dead node's containers fit on the survivors — using the RAM they actually use, not the RAM you configured.
Wire every Claude Code, Codex, and Ollama call into Prometheus and one Grafana dashboard — tokens, latency, cache hits, and real dollars vs quota burn.
How this site captures real, publish-safe homelab screenshots — a throwaway demo lab plus headless Chrome, with no mockups and no leaked IPs.
My Uptime Kuma monitors logged 24 hours of red while every service was up. Inside a Docker container, localhost isn't your machine — here's why, and the fix.
Use Network UPS Tools (NUT) so a single UPS can cleanly shut down every machine in your homelab when the power fails — one server, many network clients, step by step.