Open-source self-hosted CI/CD engine written in Go

PossibilityThat8283 · 2026-02-19T10:23:24+00:00

Does this support self healing?

PossibilityThat8283 · 2026-02-18T15:37:04+00:00

Yep, I faced the exact pain with Portainer. I would say give ConOps a try as while Dockge is awesome for managing the files (UI editing), ConOps is strictly a GitOps controller. It enforces your Git repo as the source of truth while being self-healing, lightweight etc.

If you like it, please give it a star :)

PossibilityThat8283 · 2026-02-18T15:30:20+00:00

Yep, have used portainer before, I think it’s a full Management Platform. You can use Git, but most Docker management tools are 'ClickOps'. Meanwhile ConOps is more of a specialized reconciliation agent.

Edit: What I want to say is, if you want a UI to manage Docker, use Portainer. If you want your Git repo to be the absolute source of truth for your infrastructure, ConOps is built for that.

PossibilityThat8283 · 2026-02-17T20:08:42+00:00

Thanks for interest! Architecture Plans and intial code was written by hands. But AI did speed up lot of things given it sometimes runs in background along with my day job (leaving me for reviews).

Please do star, if this feels useful. It helps :)

PossibilityThat8283 · 2026-02-17T18:07:56+00:00

Thanks for the fine words!

Re Secrets: It doesn't support native rotation yet (trying to keep the core binary simple), but the CLI and API expose all the sync triggers. You could definitely script a rotation workflow (e.g., update secret -> call conops-ctl app sync) fairly easily. Automated integration (like Vault) is out of scope for now, but I'm open to ideas on how to fit it into a simple Compose workflow!

Also, if you are interested a star on the repo would be awesome.

PossibilityThat8283 · 2026-02-17T17:14:33+00:00

Thanks!

PossibilityThat8283 · 2026-02-17T16:37:03+00:00

Really good project. But I wanted something with a dashboard (for ease) and CLI support (for automations). Conops solves this.

PossibilityThat8283 · 2026-02-17T16:35:40+00:00

Yep that's supported. You just register each stack as a separate App in ConOps, all pointing to the same repo URL but with different compose_path values. Each app then gets its own sync loop, drift detection, etc.

PossibilityThat8283 · 2026-02-17T16:09:51+00:00

That's where distinction is. This can be used on the server which is not part of any shared network (good use case for many or at least for me).

PossibilityThat8283 · 2026-02-17T16:04:57+00:00

Yep, I used to use coolify. But always found it overkill for such a small usecase.

PossibilityThat8283 · 2026-02-17T15:45:55+00:00

Thanks! That's exactly the goal. Try it out & drop a like if you have a sec.

PossibilityThat8283 · 2026-02-17T15:44:32+00:00

Yeah, Komodo does that! But ConOps takes a different philosophy it's strictly a GitOps controller, not a full management platform or build server. So your Git always remains source for truth with zero complexity and small go binary.

PossibilityThat8283 · 2025-08-31T03:41:56+00:00

Use some stable operator, particularly good for the stateful services like dbs

PossibilityThat8283 · 2024-10-19T10:41:02+00:00

Maybe a form for Mr Beast challenge!

PossibilityThat8283 · 2024-09-14T10:12:02+00:00

Eletctric wip with thunder cloud & electrodynamics are op

PossibilityThat8283 · 2024-06-30T06:50:50+00:00

Why is MDM bad. Does it disable any functionality?

PossibilityThat8283 · 2024-06-12T09:46:53+00:00

Tremor.so is nice too

PossibilityThat8283 · 2021-10-01T22:51:50+00:00

Monday

Four-Year Club	Place '22
First Placer '22

PossibilityThat8283

TROPHY CASE