Hacker News Reader

Comment by YaBa | Hacker News Reader

Use locally installed Gitea. I only use Github for public forks and nothing else. Personal projects are all on private Gitea.

View on HN

Not to add to the noise, but I've switched to Forgejo. It was very easy to migrate (as Forgejo is just a fork of Gitea, even has references to Gitea in a lot of places, like env variable names), and I've been very happy with it for the past ~6 months.

What is changed in Forgejo compared to Gitea? If the only difference is the name, Gitea is a better name.

Gitea have moved the product from a community governed product to an open core one and handed over the gitea.com domain to a hosted services vendor

My question was: what did Forgejo do? If the software is still developed in Gitea's repository, and all Forgejo does is download the source from gitea.com, rename it, and post it on forgejo.org... how does that help the users?

If there exists some Gitea features that are not available open source ("open core")... how does having Forgejo help? Unless they provide those features, the situation remains unchanged. Until they do, what is there to applaud, and what's the point of switching?

Luckily Forgejo has a blog with a days-old blog post that spells this out. The winds are clearly blowing in Forgejo's direction despite some doubt from me, early on.

The "we're becoming a hard fork"[0] blog post says that they are hard-forking and what the consequences of that will be, but says nothing about why.

[0]: https://forgejo.org/2024-02-forking-forward/

The "why" was explained by another commentor. They became hostile to their community, pulling a bunch of features out of reach and moving previously free features behind paywalls. They're moving to target more enterprise customers, and as a personal user, I don't want to be limited in this way, so I've switched to the community fork (Forgejo)

Did you get an answer to my question there? I didn't...

Why did Gitea seem to win out in the self-hosted space over GitLab?

I know gitea is extremely lightweight. I used to host Gitlab years ago and it took way more resources. It seems like hosting it is more geared toward enterprises than individuals/very small teams.

Because it runs on the lowest vps you can imagine, GitLab is way overkill for personal projects.

Gitea is simple to package and run, so I just install a single package and enable a systemd service.

Gitlab is really designed to run on kubernetes, and while there's plenty of self hosters willing to run overkill infra locally, has proved to be enough of a pain for enough people to run that it limited its growth in that space.

Reply on news.ycombinator.com