> I'm really excited about Forgejo

Our product studio with currently around 50 users who need daily git access moved to a self hosted forgejo nearly 2 years ago.

I really can’t overstate the positive effects of this transition. Forgejo is a really straightforward Go service with very manageable mental model for storage and config. It’s been easy and cheap to host and maintain, our team has contributed multiple bugfixes and improvements and we’ve built a lot of internal tooling around forgejo which otherwise would’ve required a much more elaborate (and slow) integration with GitHub.

Our main instance is hosted on premise, so even in the extremely rare event of our internet connection going offline, our development and CI workflows remain unaffected (Forgejo is also a registry/store for most package managers so we also cache our dependencies and docker images).

▲

xrd 5 hours ago | parent [-]

Wait, forgejo offers a built-in container registry? How does that work? I don't see that in the admin section at all.

▲

isodev 5 hours ago | parent | next [-]

Container registry and a lot more, they call it Package registry in the docs https://forgejo.org/docs/latest/user/packages/

▲

irusensei 4 hours ago | parent | prev [-]

Just run podman or docker login your.forgejo.instance.address then push to it as normal. An existing repo must exist. You can check the images under site administration -> packages.

Speaking of authentication it also works as an openid provider meaning you can authenticate every other web software that supports it to Forgejo... which in turn can look for users in other sources.

It also has wikis.

Its an underrated piece of software that uses a ridiculous small amount of computer resources.

	▲	xrd 4 hours ago \| parent [-]
		That's so brilliant. Wow. I'm struggling to wrap my brain around how they not only support OCI (docker) but also APK (alpine) and APT (debian) packages. That's a very cool feature.