3 ms·
Wait, forgejo offers a built-in container registry? How does that work? I don't see that in the admin section at all.
by xrd 10mo ago
Wait, forgejo offers a built-in container registry? How does that work? I don't see that in the admin section at all.
- isodev 10mo agoContainer registry and a lot more, they call it Package registry in the docs https://forgejo.org/docs/latest/user/packages/ https://forgejo.org/docs/latest/user/packages/
- p2detar 10mo agoIs it not the same as in Gitea? https://docs.gitea.com/usage/packages https://docs.gitea.com/usage/packages edit: Ok, this answers my question: https://forgejo.org/compare-to-gitea/#is-there-a-list-of-features-forgejo-has-over-gitea https://forgejo.org/compare-to-gitea/#is-there-a-list-of-fea...
- deleted 10mo ago[deleted]
- irusensei 10mo agoJust 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 10mo agoThat'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.