this post was submitted on 11 Mar 2026
91 points (98.9% liked)

Selfhosted

57442 readers
476 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Update

Forgejo seemed to be the winning answer so I tried setting it up. Total setup time was less than 10 minutes. I pushed 10 repositories to test it out and so far it seems pretty good. Thank you everyone for the answers!


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!

you are viewing a single comment's thread
view the rest of the comments
[–] lime@feddit.nu 53 points 1 day ago* (last edited 1 day ago) (2 children)

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

[–] Serinus@lemmy.world 4 points 1 day ago (3 children)
[–] DaPorkchop_@lemmy.ml 1 points 22 hours ago

Jenkins has fairly solid Gitea/Forgejo integration :)

[–] PotatoesFall@discuss.tchncs.de 1 points 1 day ago (1 children)

forgejo supports woodpecker CI I thought?

[–] eodur@piefed.social 5 points 21 hours ago (1 children)

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!

[–] lime@feddit.nu 1 points 1 day ago

just use a make file like a civilised human being

[–] fizzle@quokk.au 1 points 1 day ago

I would like to use bare repos because I don't share with anyone else and don't really need the web-ui for issues or wikis or anything.

However, I need git-lfs and if I understand correctly, that doesn't wont work with a bare repo over ssh.

I was using gitea a while back and they had a way to dump repos and db, but there didn't seem to be a way to restore. That being the case I switched to gogs which has been great. It was only recently I learned that gogs wasn't very active and there was some kind of security breach. Mine is only accessible on my LAN so not particularly worried about security.

Anyhow, looking at forgejo now it seems like there still isn't a great way to restore from backup? I guess that might not matter to me if I'm only interested in the repos and no comments or other stuff that might be in the database.