this post was submitted on 11 Mar 2026
99 points (99.0% liked)

Selfhosted

60409 readers
204 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] SpaceNoodle@lemmy.world 10 points 3 months ago* (last edited 3 months ago) (1 children)

Why forgejo instead of gitea?

[–] Creat@discuss.tchncs.de 15 points 3 months ago* (last edited 3 months ago) (1 children)

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 between the teams. 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 allowing you to go back and forth between the two, it's now an active conversion, I think.

[–] SpaceNoodle@lemmy.world 12 points 3 months ago* (last edited 3 months ago) (1 children)

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.

[–] moonpiedumplings@programming.dev 4 points 3 months ago (1 children)

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.

[–] SpaceNoodle@lemmy.world 2 points 3 months ago

Good to know, I'll look into it this weekend.