Looking into possibly replacing my GitLab instance, as I find it bloated and heavy on both hardware and maintenance compared to alternatives.
Currently I’m looking at:
So I’m wondering what the people on here use, and if they have any other suggestions or opinions?
Do you need ci/cd or only git? If just git, gitea or forgejo are super simple.
If you don’t need multiple users or a web ui, you could also just use ssh and store git repos on a server somewhere without extra services running:
https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server
since 1.19 Gitea supports CI/CD action runners that are compatible with github actions. I have one that generates a static site from the data I store in gitea and publishes it to netlify.
Gitea is light and fast so I highly recommend it. If you are worried about it being a for profit company, then use the fork, but if they haven’t done any harm, I’d said give them a shot.
Are there any feature differences between gitea and forgejo?
I can’t figure out any differences other than the ownership structure.
Forgejo is about to introduce support for federation, but is also planning to upstream those changes to GitTea down the line
I tried it at one point and they hadn’t even done a find/replace on “gitea”, so it would seem the changes, if any, are pretty minimal.
I’m using Gitea. I did try OneDev and it is very nice, but mainly intended for single-team usage as it doesn’t use different namespaces for user projects. It’s also very much its own thing, with its own CI/CD for example. Gitea can integrate with other projects much better, like using Woodpecker for CI/CD or logging in with GitHub/GitLab using Oauth.
I did follow the drama around Gitea/Forgejo, but for now the Gitea company hasn’t done anything wrong, there’s no feature difference (Forgejo aims to be a soft-fork for the moment) and Forgejo had a bit of drama around the lead developer ~1 month after it was founded.
I assume that by now you’ve made a decision, so if I may I’d like to chip in and ask what’s the benefit of self-hosting a Git instance, like the ones mentioned, over using existing free services like GitHub or Codeberg to host your code? What do you gain by hosting this yourself, apart from privacy and security?
I’d say the main benefit gained is sovereignty and a sense of place. This is not for personal use, but rather for a computer enthusiast association that I’m part of, so having our own git to integrate with the rest of our services makes sense. Throw on branding and link it to our SSO.
Maybe sourcehut if you need more than git hosting.
if you have a hard time choosing between Gitea and Forgejo I recommend picking Gitea for now, as they haven’t done anything bad just yet, but if they do Forgejo supports migration from Gitea.
iirc there isn’t an official way of migrating the other way so if Forgejo fucks up you may end up out of luck
Are the alternatives feature-complete in regards to GitLab CE?
Big fan of Gogs personally. Simple, light and a doddle to install.
Gitea is a fork of Gogs
+1 for Forgejo. It is super lightweight but still has all the common features. It also is not run by a for-profit corporation but is fully community-driven and maintained by a non-profit association everyone can become a member of.
My friend has deployed Phorge for himself and appears to be happy with it.
What do you mean by “gitea turned into a for profit”?
I really like gitea, set it up at my last job and it was easy to work with and used very little resources.
What do you mean by “gitea turned into a for profit”?
https://lemmy.world/comment/1377774 - it’s FUD. Forgejo is also backed by a company, by the way [1]
You can read their blogpost about it here: https://blog.gitea.com/a-message-from-lunny-on-gitea-ltd.-and-the-gitea-project/
It resulted in Codeberg launching their own fork: https://blog.codeberg.org/codeberg-launches-forgejo.html
I’m on https://github.com/charmbracelet/soft-serve and like it very much. It couldn’t be any simpler. As long as you don’t need PR/MR features and full blown web UI it’s a really good choice IMHO.
Certainly looks interesting, though being able to do code review and a more full-fledged CI/CD solution is a requirement.