Comment by homebrewer

Comment by homebrewer 3 days ago

Ease of maintenance is an even bigger difference. We've been using gitea for a bit over five years now, and gitlab for a few years before that, and gitea requires no maintenance in comparison. Upgrades come down to pulling the new version and restarting the daemon, and take just a few seconds. It's definitely the best solution for self-hosters who want to spend as little time as possible on their infrastructure.

Backups are handled by zfs snapshots (like every other server).

We've also had at least 10× lower downtime compared to github over the same period of time, and whatever downtime we had was planned and always in the middle of the night. Always funny reading claims here that github has much better uptime than anything self-hosted from people who don't know any better. I usually don't even bother responding anymore.

veeti 3 days ago

I guess I'll just chime in that while Gitlab is a very heavy beast, I have self hosted it for over a decade with little to no issues. It's pretty much as simple as installing their Omnibus package repository and doing apt install gitlab-ce.

Reply View 0 replies

c-hendricks 3 days ago

When I self hosted gitlab I never found the maintenance to be that bad, just change a version in a compose.yml, sometimes having to jump between blessed versions if I've missed a few back to back.

Like others, I've switch to Gitea, but whenever I do visit gitlab I can't help but think the design / UX is so much nicer.

Reply View 4 replies

dvdkon 3 days ago

My usual impression of GitLab is that it has too many functions I don't ever use, so the things I actually do want (code, issues, PRs, user permissions) are needlessly hidden. What's your workflow that you find GitLab's UX to be nicer than Gitea's?

Reply View | 3 replies
- c-hendricks 3 days ago
  
  For instance I just got tripped trying to sign out of my gitea instance since the mobile design has two identical looking avatar + username blocks on top of each other, one being the org switcher the other being a menu (with no indicator) with the sign out button.
  I went to a project page, and it auto focused the search input (???), causing a zoom in on mobile.
  I just prefer the design / look + feel of gitlab more than gitea/forejo. It's not really a hot take, gitlab has been around a lot longer and has much more support.
  
  Reply View | 0 replies
- mbreese 3 days ago
  
  That was my take too. It is a big project with a lot of functionality. But, I never needed all of that functionality, so it just seemed bloated to me. I switched over to Gitea for self-hosted code repositories (non-public repos behind a firewall) a while back and haven't had any issues thus far.
  
  Reply View | 0 replies
- flaburgan 3 days ago
  
  You can pin those you want in the left menu
  
  Reply View | 0 replies

estimator7292 3 days ago

I found gitea's interface to be so unusably bad that i switched to full-fat GitLab.

Gitea refused to do some perfectly sensible action- I think it had something to do with creating a fork of my own repo. Looking online, there's zero technical reason for this, and the explanation given was "this is how GitHub does things". Immediately uninstalled. I'm not here for this level of disrespect.

Reply View 1 reply

mroche 3 days ago

I found gitea's interface to be so unusably bad that i switched to full-fat GitLab.
Was this Gitea pre-UI redesign or after? 1.23 introduced some major UI overhauls, with additional changes in the following releases. Forejo currently represents the Gitea 1.22 UI, reminiscent of earlier GitHub design.

Reply View | 0 replies

dsassoli09 2 days ago

I find Gerrit to also be very low maintenance.

If you have a high-availability or multi-site set-up you also don't need to take any downtime to upgrade.

Reply View 0 replies