Edit: it seems like my explanation turned out to be too confusing. In simple terms, my topology would look something like this:

I would have a reverse proxy hosted in front of multiple instances of git servers (let’s take 5 for now). When a client performs an action, like pulling a repo/pushing to a repo, it would go through the reverse proxy and to one of the 5 instances. The changes would then be synced from that instance to the rest, achieving a highly available architecture.

Basically, I want a highly available git server. Is this possible?

I have been reading GitHub’s blog on Spokes, their distributed system for Git. It’s a great idea except I can’t find where I can pull and self-host it from.

Any ideas on how I can run a distributed cluster of Git servers? I’d like to run it in 3+ VMs + a VPS in the cloud so if something dies I still have a git server running somewhere to pull from.

Thanks

  • ryokimball@infosec.pubEnglish
    2·
    3 days ago

    So, to be clear, GitHub is not git. Git is intrinsically distributed. GitHub is basically a repository Management service.

    I did some googling for about 10 seconds and afaik GitHub does not support any type of self hosting. I know you can selfhost gitlab , but I don’t see a project for either GitHub or gitlab called spokes.

    Not knowing anymore than this about what you actually want to accomplish, my advice would be to just figure out how to run your own git server (without the management fluff) and do a 3-2-1 backup scheme. You could of course also create a gitlab instance with an HA set-up, plus backing that up to the cloud.

    • marauding_gibberish142@lemmy.dbzer0.comOPEnglish
      11·
      3 days ago

      GitHub didn’t publish the source code for their project, previously known as DGit (Distributed Git), now known as spokes. The only mention of it is in a blog post on their website but I don’t have the link handy right now

    • marauding_gibberish142@lemmy.dbzer0.comOPEnglish
      11·
      3 days ago

      Apologies for not explaining it properly. Essentially, I want to have multiple git servers (let’s take 5 for now), have them automatically sync with each other and run a loadbalancer in front. So when a client performs an action with a repository, it goes to one of the 5 instances and the changes are written to the rest.

      I have edited the post, hopefully the explanation makes more sense now