Self-Configuring GitOps for Proxmox: Recursive LXC Automation as Code

GitHub: stevius10/Proxmox-GitOps

⸻

What it is

Proxmox-GitOps is a self-configuring CI/CD environment for Proxmox LXC.
It manages container provisioning, configuration, and orchestration using an infrastructure-as-code workflow.
All automation is version-controlled and idempotent.

⸻

How it works
• Bootstrap locally in Docker (one command)
• CI/CD pipeline pushes codebase into a Gitea instance
• Recursive self-configuration: The pipeline triggers itself in every new container environment (“pipeline within a pipeline”)
• Provisioning with Ansible (Proxmox API)
• Configuration with Chef/Cinc (application logic)
• Consistent, modular: base config and workflows apply to all services, changes propagate automatically

⸻

• Self-managed, self-verifying infrastructure
• Full lifecycle: bootstrapping, deployment, configuration, validation
• Recursive, idempotent execution
• Modular and extensible (add container modules, adapt pipelines)
• Pure GitOps: all state and change managed via commits and PRs

⸻

Who is this for?

Primarily built for my own homelab, but extensible for anyone who wants to automate and codify their Proxmox environment—without manual steps.

⸻

Feedback

This project is still young and likely has rough edges.
I would be very interested in technical feedback, ideas, or just what you are thinking.
So, if you’re into Proxmox, GitOps, CI/CD, and infrastructure-as-code - or just to moan together recursion in an actually not idempotent Git based automation — feel free to check it out 🙂

⸻

GitHub: stevius10/Proxmox-GitOps