Proxmox-GitOps

initially driven by the question of what a Proxmox-based GitOps automation could look like and how it could be organized. Core Concepts: - Recursive Self-management: Control plane seeds itself by pushing its monorepository onto a locally bootstrapped instance, triggering a pipeline that recursively provisions the control plane onto PVE. - Monorepository: Centralizes infrastructure as comprehensive IaC artifact (for mirroring, like the project itself on Github) using submodules for modular composition. - Single Source of Truth: Git represents the desired infrastructure state. - Loose coupling: Containers are decoupled from the control plane, enabling runtime replacement and independent operation. It's a noncommercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like? I'd love to hear your thoughts!

m architecture for a self-contained, bootstrappable system - a generic IaC abstraction (customize, extend, .. open standards, base package only, .. - you name it ) that automates the entire infrastructure. It was initially driven by the question of what a Proxmox-based GitOps automation could look like and how it could be organized. Core Concepts - Recursive Self-management: Control plane seeds itself by pushing its monorepository onto a locally bootstrapped instance, triggering a pipeline that recursively provisions the control plane onto PVE. - Monorepository: Centralizes infrastructure as comprehensive IaC artifact (for mirroring, like the project itself on Github) using submodules for modular composition. - Git as State: Git repository represents the desired infrastructure state. - Loose coupling: Containers are decoupled from the control plane, enabling runtime replacement and independent operation. Over the past few months, the project stabilized, and I’ve addressed many questions you had in Wiki, summarized to documentation, which should now covers essential technical, conceptual, and practical aspects. I’ve also added a short demo that breaks down the theory by demonstrating the automation of an IaC stack (Home Assistant, Mosquitto bridge, Zigbee2MQTT broker, snapshot restore, reverse proxy, dynamically configured via PVE API), with automated container system updates and service checks. What am I looking for? It's a noncommercial, passion-driven project. I'm looking to collaborate with other engineers who share the excitement of building a self-contained, bootstrappable platform architecture that addresses the question: What should our home automation look like? I'd love to hear your thoughts!