As the title states, I am looking to host maybe ~100 git repositories locally on my home network.
I’m not planning on doing anything too crazy with my repositories. The solution doesn’t need to support like 1000s of contributors however it should support the most basic features such as being able to see individual commits, branches, diffs, maybe some PR related mechanism, a web GUI, etc.
I don’t like to tinker too much. The solution should work and be stable. Stability is a hard requirement. I want to write code and not have to worry about losing it. Yes I will make backups.
Please let me know what some of the best options are at the moment. Thank you!
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 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.
Just host a bare git repo.
I’d prefer it to have a website UI just in case I want to take a quick look at something when I’m not home.
Over a VPN, right? I always recommend not exposing services to the Internet if you can avoid it.
Jokes aside, yes.
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
I personally don’t host yet anything, but do know of a friend with a functional Gitea at home
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.
Same, but fuck the docker overhead
Didn’t use docker then fairly sure there is a Deb for it.
Just curious - what do you mean by the docker overhead?
CPU, RAM, disk space, network translation, management abstraction, buried logs …
why gitea instead of forgejo?
Why forgejo I stead of gitea?
Forgejo was soft forked from Gitea after they went commercial and changed the license (I think). If there aren’t any so far, expect pay walled features eventually.
Forgejo turned into a hard fork after communication issues, I haven’t looked too deeply into it (as I don’t really care about the fact that it’s a hard fork now). This means while it used to be a drop-in replacement showing you to go back and forth between the two, it’s now an active conversion i think.
Thanks for answering my question instead of only downvoting like half the other chuckleheads. Guess I’ll migrate to Forgejo if my Gitea instance ever gets too old.
You should probably migrate now, forgejo is currently a soft fork that is fully compatible, but in the future they are planning to hard fork and not be compatible. Well, they are in the process of doing so right now.
Good to know, I’ll look into it this weekend.
Forgejo didn’t exist when I installed gitea.
I’ve used Gitea before, Frogejo also looks pretty good
Forgejo is the way
if it wasn’t for the webui, a bare git repo would suffice. any repo can be a remote. it’s distributed, after all.
if you wanna be extra you can host git-pr
But ci/cd though
just use a make file like a civilised human being
forgejo supports woodpecker CI I thought?
Why not forgejo’s built in ci/cd? Its worked great for me so far?
I didn’t even know that’s a thing! Looks like it’s somewhat new. What a time to be alive!
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.
Self-hosting gitlab?
Surely this is the correct answer.
GitLab is awesome and has good CI-CD
Forgejo + Tailscale. Forgejo is the app behind Codeberg so it’s battle tested. I switched to it from Gitea after the controversy.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters Git Popular version control system, primarily for code SSH Secure Shell for remote terminal access VPN Virtual Private Network
3 acronyms in this thread; the most compressed thread commented on today has 19 acronyms.
[Thread #157 for this comm, first seen 11th Mar 2026, 23:20] [FAQ] [Full list] [Contact] [Source code]
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.
It’s monstrous, but gitlab installs from one big RPM on a base box; and with one config file you’re up.
While I agree, out of the box the configs ARE NOT for home lab use.
For sure. And their bumbling has made it harder to deactivate all the useless bloat and get the good web-editor back. And a host of other mind-numbingly short-sighted decisions that show they’re fully run by LostBoy coders who were never mentored and just don’t know better.
But tuning can come after. And their CI is way fucking better than forgejo’s facepalm of a GitHub clone. And that’s a thin reason, but, yeah.
