if it wasn't for the webui, a bare git repo would suffice. any repo can be a remote. it's distributed, after all.

forgejo is the most popular choice right now.

if you wanna be extra you can host git-pr

Forgejo + Tailscale. Forgejo is the app behind Codeberg so it's battle tested. I switched to it from Gitea after the controversy.

I finally decided to make the move off github a couple weeks ago and ended up self hosting with Forgejo. It was really easy to set up, and my buddies and I are loving it. Provides a robust web interface and handles pull requests with automatic merges and all that. I haven't had any issues thus far

Forgejo is the way

Gitea is the answer, configure/install with docker. I have had mine going for a few years now and haven't had to touch it besides updating the docker container which I automated.

I love Forgejo, I'm glad you are happy with it too. Their upgrade process is pretty minimal/straightforward (at least it has been so far) and their runner configuration is a bit heavy to set up initially (I maybe took the security recommendations a bit too intensively despite the fact that I'm running a completely private site, but allowing systems that run arbitrary commands automatically is legitimately a bit intimidating) but has been really nice and reliable now that it's working.

If you're looking for a bare bones solution, and you already have a machine that you can SSH into, you could just use that. There are desktop GUI/TUI apps galore that you can use to inspect commits, branches and such.

At work I'm in the process of planning a move from Subversion to Git. So I've been looking at Forgejo, a hard fork of Gitea maintained by Codeberg. It has all the important features of other forges like GitLab and Gitea. But is completely open source.

I've used Gitea before, Frogejo also looks pretty good

Just host a bare git repo.

If all of the below doesnt work out, you can host git by itself. I did that at an office once.

https://gist.github.com/Kreijstal/28fc987270b71849505bbc89b3f2d90a steps look correct.

But for me forgejo worked out well for my side projects and mirroring.

I’ve set up a few gitlab servers at companies and it’s always been well received. Doing it from scratch may be more complex than you want, but I think there are docker images for a more turnkey type solution. And the option of building CI/CD pipelines in the future is always nice to have.

Forgejo seemed to be the winning answer so I tried setting it up. Total setup time was less than 10 minutes.

Just a heads up... I haven't looked at this since forever ago (when foregjo was gitea), but make sure you have a restore plan. I think there's a dump command but no restore.

It's monstrous, but gitlab installs from one big RPM on a base box; and with one config file you're up.

Relevant:

https://en.wikipedia.org/wiki/Forge_(software)

I second the option of Git + SSH. That will scale to one hundred repos. And if you don't want the repos to be checked out, use "git clone -n" to not do that. It'll just be dozens of repos which only have the minimal .git/ directory. All other repos that specify this one as the upstream will have no issues pulling or pushing code.

You won't have PR features nor a web UI though.

Self-hosting gitlab?

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

3 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.

[Thread #157 for this comm, first seen 11th Mar 2026, 23:20] [FAQ] [Full list] [Contact] [Source code]

I personally don’t host yet anything, but do know of a friend with a functional Gitea at home

I'd go for Forjego or Gitea.