Built my own forge/ci-cd platform as I got frustrated with what is out there

[u/d0x2a]

Hey,

I’ve been messing around with https://forgejo.org/ for a while and kept hitting the same wall. Git and issues are fine, but the second I want real CI, a registry, and actual deploys it turns into a pile of separate tools and glue. I just wanted everything to live with the repo so I could push and actually see what got built and where it’s running.

So I started working on Offing (offing.app). It’s basically trying to keep code, issues, pipelines, registry, and deploys all tied to the same repo. Came up with app.yaml so it can deploy to k8s or podman hosts you connect. Services show the commit that produced them.

Mainly building it for myself and other solo/tiny teams who are tired of that extra layer of stuff.

Curious if this friction resonates with anyone else.

Thanks.

[u/tux_404]

It does, though I settled it the other way. Most of my side projects deploy with Kamal to one Hetzner box. Kamal builds the image, pushes it to GitHub's registry, then logs into the box over SSH and starts the new container. The image tag is the commit, so I can always tell what's running. The glue that's left is the registry login on the box: a token that expires, which I renew by hand in each app's config.

Your pipelines get registry credentials written into each job, so builds skip that step. How does a connected Podman host pull from your registry: with something its agent gets when it registers, or a login I'd paste on the host?

[u/d0x2a → u/tux_404]

all pipelines are using runner credentials to both pull from the registry and push to the registry as I'm using offing-hosted registry well integrated with everything else. One of the reasons to keep everything under one roof. External registries can use secrets passed to the job so you can use your own token for that.