← Back to context Comment by lrvick 8 days ago We recommend Codeberg/Forgejo now since it is better in every way, and Gitlab went corpo. 7 comments lrvick Reply NewJazz 8 days ago Gitlab was always for profit.And forgejo doesn't have feature parity at all with gitlab. Neither does github, for that matter.Just take a look at how to push container images from a cicd pipeline in gitlab vs. Forgejo. fmbb 8 days ago What’s the difference?Pushing images is a oneliner. NewJazz 8 days ago In gitlab, yes (well, two lines, login then push). In forgejo, there is no cicd token that gives you scoped access to the built in container registry. You must create a long lived token and add it as a secret to the repo you want to push from.See here: https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-fo... pfcd 8 days ago > We recommend Codeberg/Forgejo now since it is better in every way...Lol.> ...and Gitlab went corpo.How else will they sustain/maintain such a product and compete with the likes of GitHub? With donations? Good luck. Elucalidavah 8 days ago Are those any better than self-hosted gitlab, or do you only mean central-hosted usage? NewJazz 8 days ago Codeberg is central hosted so I think they mean in general.
NewJazz 8 days ago Gitlab was always for profit.And forgejo doesn't have feature parity at all with gitlab. Neither does github, for that matter.Just take a look at how to push container images from a cicd pipeline in gitlab vs. Forgejo. fmbb 8 days ago What’s the difference?Pushing images is a oneliner. NewJazz 8 days ago In gitlab, yes (well, two lines, login then push). In forgejo, there is no cicd token that gives you scoped access to the built in container registry. You must create a long lived token and add it as a secret to the repo you want to push from.See here: https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-fo...
fmbb 8 days ago What’s the difference?Pushing images is a oneliner. NewJazz 8 days ago In gitlab, yes (well, two lines, login then push). In forgejo, there is no cicd token that gives you scoped access to the built in container registry. You must create a long lived token and add it as a secret to the repo you want to push from.See here: https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-fo...
NewJazz 8 days ago In gitlab, yes (well, two lines, login then push). In forgejo, there is no cicd token that gives you scoped access to the built in container registry. You must create a long lived token and add it as a secret to the repo you want to push from.See here: https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-fo...
pfcd 8 days ago > We recommend Codeberg/Forgejo now since it is better in every way...Lol.> ...and Gitlab went corpo.How else will they sustain/maintain such a product and compete with the likes of GitHub? With donations? Good luck.
Elucalidavah 8 days ago Are those any better than self-hosted gitlab, or do you only mean central-hosted usage? NewJazz 8 days ago Codeberg is central hosted so I think they mean in general.
Gitlab was always for profit.
And forgejo doesn't have feature parity at all with gitlab. Neither does github, for that matter.
Just take a look at how to push container images from a cicd pipeline in gitlab vs. Forgejo.
What’s the difference?
Pushing images is a oneliner.
In gitlab, yes (well, two lines, login then push). In forgejo, there is no cicd token that gives you scoped access to the built in container registry. You must create a long lived token and add it as a secret to the repo you want to push from.
See here: https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-fo...
> We recommend Codeberg/Forgejo now since it is better in every way...
Lol.
> ...and Gitlab went corpo.
How else will they sustain/maintain such a product and compete with the likes of GitHub? With donations? Good luck.
Are those any better than self-hosted gitlab, or do you only mean central-hosted usage?
Codeberg is central hosted so I think they mean in general.