What is the best self hosted git server [Gitea or GitLab]?

[stares at error messages]

I'm interested in integration with Kuberntes. Continues Integration is most important feature I'm looking for. Just having a web git interface is not that important on it's won. I'm open to other options, but they have to be establish, not some very new buggy project, and need to have good continuous integration job runner. I have heard that GitLab is hard to update. Is this still true? When updating does the data on the server get preserved or do all the repos have to be recreated?

 

[Rango Dango]

cgit

 

[stares at error messages]

cgit

How does cgit work with continuous integration?

 

[Dreamland]

Only have experience with selfhosting Gitea, i like the mirror/scrape feature so it can double as a backup-system for endangered repos.

I'm not up to date on the CI features on it however, the scripts i make myself are too small in scope for that.

 

[Rango Dango]

How does cgit work with continuous integration?

idk

 

[Anti Snigger]

I use forgejo and I like it a lot

 

[Soggy Floppa]

Gitlab has good CI, idk about updating it

 

[monk]

Gitea is way less bloated than Gitlab. It eats a lot less resources and is a lot easier to set up. Gitea is almost entirely just one executable. I'd argue that maybe even Gitea is overkill depending on what you need to do.

I mean, look at this nightmare:

https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/production/architecture/

Are you going to be able to sleep at night with that many interconnected shit?
Granted, it's what Gitlab have for their production serrvers, you probably don't need half of that, but it's still way more complicate than alternatives.

To be pretty suckless and minimal you could use Gitolite. If you want a web frontend, you could add cgit as a read only web frontend on top of that. For CI write your own scripts as git hooks (post-receive or whatever) in shell.

CI sounds nice on paper. But managing it is added complexity and IMO only worth it if you work at a place that has a large amount of programmers. Anything below 5-10 it's not worth it, just have one guy that's good in scripting write good build scripts and push the artifacts yourself whenever you want to stage or release.

 

[Demonslayer1776]

If youre coming from github and want something similar please Gitea is probably the most natural solution.

 

[Ancient Pioneer]

Gitea is probably what you're looking for. It does CI and if you're inclined to it can host docker images as well, its pretty lean for what its doing and the repo layout is familiar to people who use Github. Gitlab is very heavy and full featured but its definitely the option if you were planning to be a public host with big hardware backing.

 

[stares at error messages]

From the recommendations here I've had a look at Gitea.

Good things:

• It has built in runner now. This is a change from when I looked at it years ago. They didn't have their own runner. That has changed since they've become a freemium company. https://docs.gitea.com/usage/actions/overview#runners https://docs.gitea.com/usage/actions/act-runner
• The free level has a package repository that can be enabled. It specifically mentions Helm (Kubernetes). https://docs.gitea.com/usage/packages/overview
• It supports Actions and is very similar to Github actions. Which would make someone coming from Github have an easier transition. https://docs.gitea.com/usage/action...-when-using-actions-such-as-actionscheckoutv4

Bad things:

• Gitea is dependent on Github Actions Scripts. They use the same scripts that are pulled from Github. Again, it make is easier, but it means that you are still dependent on Github. So it really is like "Github Lite" https://github.com/actions/checkout/tree/main