[thejosh]

For the forgejo side of things, this is for my own projects. Not hosting others (or for their code search, this was for mine).

For context, forgejo does have [code search](https://forgejo.org/docs/latest/user/search/code-search/), which is simple to enough.

I like forgejo/gitea - a single app.ini, postgres for the database. Done through a docker compose.

Last time I ran gitlab, it required oodles of memory - it's just me!

> You can just self-host GitLab CE and use self-hosted ElasticSearch integration to set up code search. I really don't understand the point of Forgejo, sounds like making your life harder

Sounds like more steps/maintenance/hassle and a more complicated than just using forgejo for my own personal projects, forgejo uses <120MB of memory for me, has runners, etc.

[qweqwe14]

That's all good until you discover that Forgejo is very barebones compared to GitLab, and you inevitably end up recreating GitLab featureset by using some scripts/addons from random people and pray it doesn't shit itself

Isn't it better to invest your time in setting up GitLab once and not have to deal with Forgejo being a toy project?

It literally takes 1 compose.yaml to self-host GitLab Omnibus, and 1 compose.yaml for the runner. You have been misled by suckless fans if you think that self-hosting GitLab is more complex than Forgejo.

> Last time I ran gitlab, it required oodles of memory - it's just me!

It requires what, 8GB of RAM? That's not "oodles" by any definition.

[thejosh]

If I ever need anything more advanced than what Forgejo is offering me, I'd reach for Gitlab, for sure. :-)