Proxmox-GitOps is built to manage and deploy LXC containers in Proxmox, fully defined as code and easy to modify via Pull Request. Consistent, modular, and dynamically adapting to changing environments and base configurations.
A single command (and accepting the Pull Request in the Docker environment, ha) bootstraps the recursive deployment:
- The Docker-based environment pushes its own codebase as a monorepo, referencing modular components (containers you define are automatically integrated as submodules), each integrated into CI/CD.
- The pipeline triggers itself — updating references, enforcing state, and continuing recursively.
Provisioning is handled via Ansible using the Proxmox API. Configuration is managed with Chef/Cinc cookbooks focused on application logic.
Shared configuration is applied consistently across all services. Changes to the base system propagate automatically.
It’s easily extensible, aiming to have all containers built the same way. There’s an explanation of how to do this in the README of the repository.
This project is still young and there are most likely some bugs. I built it primarily for my own homelab, but I’d like to develop it further. Would really appreciate if you are interested in The project
stevius•6mo ago
Proxmox-GitOps is built to manage and deploy LXC containers in Proxmox, fully defined as code and easy to modify via Pull Request. Consistent, modular, and dynamically adapting to changing environments and base configurations.
A single command (and accepting the Pull Request in the Docker environment, ha) bootstraps the recursive deployment:
- The Docker-based environment pushes its own codebase as a monorepo, referencing modular components (containers you define are automatically integrated as submodules), each integrated into CI/CD. - The pipeline triggers itself — updating references, enforcing state, and continuing recursively.
Provisioning is handled via Ansible using the Proxmox API. Configuration is managed with Chef/Cinc cookbooks focused on application logic. Shared configuration is applied consistently across all services. Changes to the base system propagate automatically. It’s easily extensible, aiming to have all containers built the same way. There’s an explanation of how to do this in the README of the repository.
This project is still young and there are most likely some bugs. I built it primarily for my own homelab, but I’d like to develop it further. Would really appreciate if you are interested in The project