Why forgejo over self-hosted gitlab?
Comment on Github Banned a Ton of Adult Game Developers and Won’t Explain Why
isVeryLoud@lemmy.ca 2 days agoHost your own forgejo
KickMeElmo@sopuli.xyz 2 days ago
russjr08@piefed.zip 2 days ago
Depending on what your needs and available resources are, GitLab is fairly heavy especially in comparison to Forgejo.
LodeMike@lemmy.today 2 days ago
Forgejo is also infinitely easier to run. Its a static go binary that uses an sqlite database.
KickMeElmo@sopuli.xyz 2 days ago
Fair! Mind you, the question was genuine curiosity. I don’t have projects of my own hosted at this time, but I may soon.
russjr08@piefed.zip 2 days ago
No worries at all! I battled with that choice for a while when I was self hosting. I had already been so deep into using GitLab CI that it would’ve been a pain to migrate to Forgejo Actions, though to be fair when I had setup GitLab the Actions system didn’t actually exist yet.
And if you plan to expose it to the Internet, GitLab being a much larger project has more potential security issues to keep up with which is another important note.
(Though as always when publicly exposing services to the Internet, keep up with patches either way and stay safe!)
Linearity@piefed.zip 2 days ago
Because it’s going to implement federation soon
Nobody is going to sign up to your website just to post an issue on one repository. Federation is perfect for software forges.micka190@lemmy.world 2 days ago
Maybe I’m just dumb, but I always thought half of GitLab’s features were unavailable to self-hosted instances. It’s why I just self-host Gitea and Woodpecker instead.
E_coli42@lemmy.world 1 day ago
Why not use codeberg.org?