[Thanks Drew!] Corey, On Wed, Aug 24, 2011 at 11:56 PM, Drew Northup <drew.northup@xxxxxxxxx> wrote: > > On Wed, 2011-08-24 at 17:14 +0000, Corey Mitchell wrote: >> Hello Git team, >> >> We have a distributed team (US and Japan). We are thinking about migrating from >> subversion to git because it better suits our distributed team. Due to network >> latency, we want to setup 2 git servers hosting the same repository. We want >> developers to be able to download and publish branches to their local server and >> then have those changes replicated to the other site. Is this possible? Can >> someone please explain how this setup is done? If not, can someone please >> explain the closest alternative and how it is setup? > > Corey, > If you choose to use gitolite, then you can just use Sitaram's > instructions here: > http://sitaramc.github.com/gitolite/doc/mirroring.html The code for all this is in the "mirroring-revamp" branch, by the way, although I hope to shortly bump it into pu (see below). > If nothing else, you might find it inspirational. Considering I spend more time on the docs than on the code, I sure hope it's at least that ;-) I'm currently at one of my $DAYJOB's other cities, setting up an 11-way mirrored gitolite setup for some colleagues in a different business unit. They have about 80 repos spread across 6 or 7 cities, which different repos being "mastered" at different cities. Some of them have 2 slaves, most have 1. Of those that have 2 slaves, only one needs the push *immediately* reflected. All of them have to send to a specific "backup" server sometime at night so that's like an extra slave, though developers are not expected to hit it so it doesn't need any authorisation information.. Some have enough developers that for convenience reasons they would like to have the developer push to the (local) slave and have the slave internally redirect the push to the real master, without the developer having to know where the real master is and having to configure his push-remote correctly. For developers who're working on multiple projects, with some of them mastered in one city and some in another, this is great. (I must warn that this feature is only useful when all the servers trust each others authentication, because that gets done at the slave site where the user hit, and authorisation is done on the real master taking the push). Note that this does no do exactly what you said, but probably comes close enough in some sense. So anyway it's been fun. We're halfway there, and no problems so far. Once this is up and running for a few days I will merge it into pu. regards sitaram -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html