Launched this week
Konta
GitOps for Docker Compose on low‑resource VPS
64 followers
GitOps for Docker Compose on low‑resource VPS
64 followers
Store the state of your VPS containers in a repo. Konta helps you use Git as a single source of truth, automatically sync changes with server containers using docker-compose files — no cluster, no control plane. Simply push changes to Git, and your containers will be updated automatically.
Konta
How does Konta handle a partial failure mid-sync, say one service in the compose file fails its health check while the others come up fine? ConOps and Composed do the git-pull-and-redeploy loop well, but rollback on a per-service basis without tearing down the whole stack is still manual. If Konta tracks which services changed between commits and rolls back just those, that'd set it apart for multi-app VPS setups. The no-config-migration constraint is smart... every Portainer or Coolify install ends up with more yaml managing the manager than the actual apps.
Konta
@piroune_balachandran Thanks for the question and minds!
At this moment Konta used only for deployments to automate manual steps. If a deployment fails, the stack update is considered unsuccessful. So you don’t end up with a half-switched infrastructure state. Konta tracks which services changed between commits and redeploys only changed.
I want to implement health-check feature after deployment. Because now it only verifies that containers are in a running state. With this feature Konta could decide that new vps state is broken and deployment was failed.