How nixknight/home-ops works
Project type and purpose
• This is an “Infrastructure-as-Code” and “Configuration-as-Code” repository for home-lab automation, renamed “Home-Ops.”
• It combines Terraform/Terragrunt (for VM provisioning on Proxmox), Ansible (for OS and service configuration), Docker (for service containers), and CI/CD workflows (to build container images).
File structure
• Top-level folders:
• ansible – roles, playbooks, inventories, extravars, templates
• docker – Dockerfiles and helper scripts for Kea DHCP and PowerDNS
• terragrunt – HCL modules and configs to spin up VMs on Proxmox
• .github/workflows – CI workflows to build container images
• utils – helper scripts (e.g., vault decryptor)
• Key patterns:
• Infrastructure provisioning (terragrunt) → VM hosts on Proxmox
• Configuration management (Ansible playbooks & roles)
• Container build pipeline (GitHub Actions)
• Service decomposition: DHCP (Kea), DNS (PowerDNS), Pi-hole, authentik SSO, monitoring stack (Prometheus, Grafana, Telegraf), NGINX reverse-proxy, firewall
README for additional insights
• The readme signals expansion beyond a simple Linux firewall/gateway into a fuller “Home-Ops” automation suite.
Elements
• Clear labels on each component (e.g., “Ansible Control Node,” “Proxmox VM: dhcp-server”)
• CI build & push
• VM provisioning
• Configuration / deployment flows
• Service request/response flows