It's okay. But I would definitely pick Forgejo over it for self-hosting these days. It's written in Go which is a lot better. Much faster, easier to set up, you can actually follow the code (sometimes I've had to read Gitlab's code to understand features and nearly always failed). Also no features are paid. The ones that made us eventually pay for Gitlab were mandatory reviews and merge trains. Tbh I don't think Forgejo has either of those features yet but at least when they are available they'll be free!

▲

shamiln 9 hours ago | parent [-]

Why not Gitea over Forgejo, which is what Forjego seems to be forked from?

That said, looking at recent releases, there are nice things from both, and if I wasn’t running GHES, I’d be stuck to choose between the two

▲

Macha 8 hours ago | parent | next [-]

This is gitea's homepage:

https://about.gitea.com/

This is forgejo's homepage:

https://forgejo.org/

---

The homepages should tell you which is more focused on the self-hosted open source use case.

	▲	shamiln 31 minutes ago \| parent [-]
		Both of the headline sentences on the home pages tell me they’re self-hosted. They both also have cloud options, one focussing more on large scale and features I don’t care about, the other others some sort of hosted instance that’s private. Sorry, doesn’t help me

▲

wiether 8 hours ago | parent | prev [-]

Philosophical convictions, I guess?

One is supported by a for-profit org, while the other by a non-profit org.