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!

  • lime!@feddit.nuEnglish
    39·
    3 days ago

    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

  • cecilkorik@piefed.caEnglish
    6·
    3 days ago

    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.

  • whelk@retrolemmy.comEnglish
    5·
    3 days ago

    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

  • fizzle@quokk.auEnglish
    4·
    3 days ago

    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.

  • slowtrain33@lemmy.mlEnglish
    3·
    3 days ago

    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.

  • chtk@sh.itjust.worksEnglish
    3·
    3 days ago

    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.

  • Patrick@ppb.social
    2·
    3 days ago

    @idunnololz I’m running gitea and tailscale. Sadly I had not heard of Forgejo at the time or I might have went with it instead. (Might switch over if i get bored or an itch one afternoon). Works great for me though.

  • Decronym@lemmy.decronym.xyzBEnglish
    2·
    1 day ago

    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 6 acronyms.

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

  • litchralee@sh.itjust.worksEnglish
    2·
    3 days ago

    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.

  • xombie21@lemmy.dbzer0.comEnglish
    31·
    3 days ago

    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.

        • Creat@discuss.tchncs.deEnglish
          13·
          3 days ago

          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.worldEnglish
            8·
            3 days ago

            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.devEnglish
              41·
              3 days ago

              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.