Hacker News Reader

Comment by vbezhenar | Hacker News Reader

Same in my work. We would happily spend weeks settings things up and then hours maintaining it over months, without proper backups and with abysmal security, just to save few hundreds of bucks.

I never understood that attitude, but I'm not the one who makes financial decision and tinkering with stuff is somewhat fun for me, so I don't really complain.

View on HN

Even then, GitLab is super heavyweight compared to just running Gitea. Gitea is a million times easier to set up.

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?

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.

Does Gitea offer features like continuous integration, pages, user permission management, etc?

> continuous integration

Yes: https://docs.gitea.com/usage/actions/overview

> pages

No, but if you have some sort of static content hosting set up (like a S3 bucket), it shouldn't be difficult to set up publishing to that with actions. It's also got project wikis built in.

> user permission management

Yes: https://docs.gitea.com/usage/permissions

Chiming in to request HN's current take on Gitea vs. Forgejo.

I think they are both great choices and it's a matter of personal preference.

Do you distrust the new for-profit company that owns Gitea? Do you believe that all software should be libre? Choose Forgejo.

Do you believe having a for-profit company behind gives the project more budget for feature development? Do you think that using a GPLv3 licensed software is problematic in legal terms? Choose Gitea.

It's pretty simple psychology to me - By playing around in the SWE equivalent of Home Depot all day while making a gigantic deal about the various tool manufacturers and current promotional offers, we can avoid being on the actual job site or dealing with any customers.

It's actually very easy to understand.

Employee salary is fixed expense your company is always prepared to pay every month.

Buying new software is extra new cost, which needs justification and procurement process.

Reply on news.ycombinator.com