I‘d like to share my project Proxmox-GitOps, a self-contained GitOps environment for provisioning and orchestrating Linux Containers (LXC) on Proxmox VE.

Encapsulating infrastructure within an extensible monorepository - recursively resolved from Git submodules at runtime - it provides a comprehensive Infrastructure-as-Code (IaC) abstraction for an entire, automated container-based infrastructure.

Repository: https://github.com/stevius10/Proxmox-GitOps

Demo (1min+): https://youtu.be/2oXDgbvFCWY

I started this project several months ago, originally as a personal attempt to bring industry cloud and automation patterns to my private Proxmox home server. When I shared it, I didn't expect much interest. To be honest, the response for such a niche topic has been way more than I could have imagined.

It's a platform architecture for an elegant, self-contained system. It's an attempt to build a generic IaC abstraction that manages its own lifecycle, initially driven by the question of what I wanted my own GitOps home automation to look like.

This is a non-commercial, 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: How do we want our home automation to be?

I‘d love to hear your thoughts!

——

- Recursive self-management: the control plane executes within the managed containers to maximize reproducibility and minimize drift.

- Git as current desired state: operations map to standard Git workflows (commit, merge, rollback) in a stateless management model.

- Convention-based extensibility: add a service by copying a container definition from libs, adding a minimal cookbook and `config.env`; the pipeline handles provisioning, configuration, and validation.

- Loose coupling: containers remain independently replaceable and continue to function without manual follow-up.