CI/CD works fine for selfhosted forgejo, I set mine up with minimal hassle.
Comment on Which git plateform to choose?
Mihies@programming.dev 20 hours ago
I’d say Forgejo as it is the most simple of the three. If you want more complexity (like CI/CD), then one of the other two. You can checkout Forgejo at codeberg.org.
myrmidex@belgae.social 20 hours ago
corsicanguppy@lemmy.ca 13 hours ago
Is the CI/CD still a faithful clone of github’s worst-in-show setup? Because if I had a plan for ditching GL, the CI keeps forgejo from being a contender.
Mihies@programming.dev 19 hours ago
Sure, but it’s not part of Forgejo, is it?
tedvdb@feddit.nl 18 hours ago
Mihies@programming.dev 17 hours ago
I guess it depends on how you look at it - “It needs to be installed separately.”
Gulliver@lemmy.zip 20 hours ago
Thanks for you reply, I did not know what CI/CD mean so just checked it, it’s not important for me because I want to display only finished project. Forgejo looks great and I just found it’s available as a TrueNas app which is great for me.
Ghoelian@piefed.social 13 hours ago
I’ve been running forgejo (and forgejo-runner for workflows) on TrueNAS for a little while now, without any issues really.
The runner image is also available as a TrueNAS app, so if you ever do want CI/CD it’s pretty simple to set up.
F04118F@feddit.nl 20 hours ago
Gitea is not fundamentally different, Forgejo is just a better fork of it. Better in terms of: more contributors, more users, dogfooding (Gitea is built on Github 🤦).
But yes, GitLab is like the Mac of Git forges: everything is included, doing everything their own way, vendor lock, very expensive. There is a community edition but serious users will run into its limitations and it does not integrate neatly with external solutions.
Forgejo is IMO the Linux of Git forges: low on resources, expandable, hackable, stable.
We should also keep in mind that Gitea was hostilely taken away from the community by a for-profit corporation that made Gitea open-core by hiding a way features behind a paywall in a cloud.
FUD
Gitea is still MIT licensed and the Enterprise tier features only cater to large org needs [1]
why would I want to deal with nightmarish SAML config when OIDC does the job
FACT
The corporation basically stole the project from the community and started hiding features behind a paywall.
It is completely irrelevant if you need the features that are closed and behind a paywall and are not part of the open core.
corsicanguppy@lemmy.ca 14 hours ago
No true Scot, then?
I’m running gitlab implementations at a few sites. I’ve not seen or heard of any performance limiter with a self-managed community edition that removes a tool the others still provide.
Again, this sounds FUDdy. Which ‘external solutions’ are you using that a git-push fails on? Some spaghetti of saas tendrils seems to be already a risk, but I can’t think of any other external thing that it could mess up with.
mbirth@lemmy.ml 19 hours ago
Eh, there’s not really a better/worse between Gitea and ForgeJo. Gitea is targeting business customers, ForgeJo is targeting the open source community.