Hacker News Reader

I have maintain our Gitlab instance for the last 5 years. Zero issues, and I do a sudo apt update once a month. So I guess some people thought using the manual setup was the way to go?

View on HN

I can confirm that upkeep of Gitlab is rather easy and does not take much time. Just the occasional update every few weeks. For its size it is also quite robust and the integrations it offers work well.

The only thing I can really complain about are the constant UI changes that do not actually improve anything. I fell they are just changes for change's sake to keep some frontend devs busy.

Gitlab itself was kinda pain free, but having a bunch of dedicated local runners was a bit annoying in 2019ish. It mostly worked (with k3s) until it didn't.

Which repo are you getting your GitLab .deb packages from?

Also, Debian/Ubuntu OS security updates happen a lot more often than once a month. I suggest just using unattended-upgrades, it can even auto-reboot at a convenient time of the day after Linux kernel security updates.

This is fine for our use case, because the GitLab instance is not exposed to the internet.

Reply on news.ycombinator.com