CODEWITHSUNDEEP
gitversion-controlrepositoryinfrastructure
lysergic-acid
lysergic-acid

Reputation: 20060

Managing git across multiple sites

The scenario we have is that our organization is located in a few geographical locations.

I would like to setup a git central server so each of the distributed teams can push their changes into it and share with the rest of the teams.

I am wondering what are the best options of doing such a thing.

The current 2 options i can think of are:

  1. One central server for all global teams.
  2. One central server per geographic site. Set up some sort of automatic PUSH between servers to keep in sync.
  3. Hosted solution.

While #3 is currently not an option for our organization AFAIK, are there any other options of doing so? What is the best option?

I would assume there are already some guidelines and best practices to solve this particular issue.

Upvotes: 2

Views: 144

Answers (2)

Kevin Bedell
Kevin Bedell

Reputation: 13424

My first response would be to simply setup a github 'organization' and manage your organizations private repositories through it. There are a lot of benefits -- including backup of the data being taken care of, having people who know git extremely well managing the infrastructure, etc.

But if the company can't do that for some reason, I'd recommend having a single, global repository if at all possible.

Each person can then simply clone the central repository and pull/push changes to it. Adding additional repositories adds complexities and risks like:

  • Having to backup multiple servers to make sure the repository is safe
  • having to have processes to make sure the different repositories all push / pull changes to each other.
  • Having some teams not synch their regional repository often enough.
  • Tracking bugs introduced back through commits in other repositories.

There's no real benefit to having regional servers either, as far as I can tell.

Upvotes: 1

Noufal Ibrahim
Noufal Ibrahim

Reputation: 72855

Do you really need multiple "central servers"? Why not have all the teams work with a single repository. Much of gits work is done offline and even the parts that have to talk to the network are quite optimised. I don't think you'll have trouble with having just one central repository.

Upvotes: 3

Related Questions