{"thread":{"id":"28208","subject":"master-master server setup","startedAt":"2011-08-24T17:14:18Z","lastAt":"2011-08-25T16:06:18Z","messageCount":3,"participants":["Corey Mitchell","Drew Northup","Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"174168","messageId":"loom.20110824T191218-282@post.gmane.org","threadId":"28208","inReplyTo":null,"subject":"master-master server setup","fromName":"Corey Mitchell","fromEmail":"cmitchell@cctus.com","sentAt":"2011-08-24T17:14:18Z","receivedAt":"2011-08-24T17:14:18Z","isPatch":false,"sender":{"key":"cmitchell@cctus.com","avatar":null},"body":"Hello Git team,\n \nWe have a distributed team (US and Japan).  We are thinking about migrating from\nsubversion to git because it better suits our distributed team.  Due to network\nlatency, we want to setup 2 git servers hosting the same repository.  We want\ndevelopers to be able to download and publish branches to their local server and\nthen have those changes replicated to the other site.  Is this possible?  Can\nsomeone please explain how this setup is done?  If not, can someone please\nexplain the closest alternative and how it is setup? \n \nThanks a lot,\nCorey\n"},{"id":"174172","messageId":"1314210406.14580.6.camel@drew-northup.unet.maine.edu","threadId":"28208","inReplyTo":"loom.20110824T191218-282@post.gmane.org","subject":"Re: master-master server setup","fromName":"Drew Northup","fromEmail":"drew.northup@maine.edu","sentAt":"2011-08-24T18:26:45Z","receivedAt":"2011-08-24T18:26:45Z","isPatch":false,"sender":{"key":"drew.northup@maine.edu","avatar":"https://avatars.githubusercontent.com/u/18331571?v=4"},"body":"\nOn Wed, 2011-08-24 at 17:14 +0000, Corey Mitchell wrote:\n> Hello Git team,\n>  \n> We have a distributed team (US and Japan).  We are thinking about migrating from\n> subversion to git because it better suits our distributed team.  Due to network\n> latency, we want to setup 2 git servers hosting the same repository.  We want\n> developers to be able to download and publish branches to their local server and\n> then have those changes replicated to the other site.  Is this possible?  Can\n> someone please explain how this setup is done?  If not, can someone please\n> explain the closest alternative and how it is setup? \n\nCorey,\nIf you choose to use gitolite, then you can just use Sitaram's\ninstructions here:\nhttp://sitaramc.github.com/gitolite/doc/mirroring.html\n\nIf nothing else, you might find it inspirational.\n\n-- \n-Drew Northup\n________________________________________________\n\"As opposed to vegetable or mineral error?\"\n-John Pescatore, SANS NewsBites Vol. 12 Num. 59\n"},{"id":"174235","messageId":"CAMK1S_gKrOqY1xrsQi4hQLc85yAD0NW+wJxJ31HwRQMuY9A9sA@mail.gmail.com","threadId":"28208","inReplyTo":"1314210406.14580.6.camel@drew-northup.unet.maine.edu","subject":"Re: master-master server setup","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2011-08-25T16:06:18Z","receivedAt":"2011-08-25T16:06:18Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"[Thanks Drew!]\n\nCorey,\n\nOn Wed, Aug 24, 2011 at 11:56 PM, Drew Northup <drew.northup@maine.edu> wrote:\n>\n> On Wed, 2011-08-24 at 17:14 +0000, Corey Mitchell wrote:\n>> Hello Git team,\n>>\n>> We have a distributed team (US and Japan).  We are thinking about migrating from\n>> subversion to git because it better suits our distributed team.  Due to network\n>> latency, we want to setup 2 git servers hosting the same repository.  We want\n>> developers to be able to download and publish branches to their local server and\n>> then have those changes replicated to the other site.  Is this possible?  Can\n>> someone please explain how this setup is done?  If not, can someone please\n>> explain the closest alternative and how it is setup?\n>\n> Corey,\n> If you choose to use gitolite, then you can just use Sitaram's\n> instructions here:\n> http://sitaramc.github.com/gitolite/doc/mirroring.html\n\nThe code for all this is in the \"mirroring-revamp\" branch, by the way,\nalthough I hope to shortly bump it into pu (see below).\n\n> If nothing else, you might find it inspirational.\n\nConsidering I spend more time on the docs than on the code, I sure\nhope it's at least that ;-)\n\nI'm currently at one of my $DAYJOB's other cities, setting up an\n11-way mirrored gitolite setup for some colleagues in a different\nbusiness unit.  They have about 80 repos spread across 6 or 7 cities,\nwhich different repos being \"mastered\" at different cities.\n\nSome of them have 2 slaves, most have 1.  Of those that have 2 slaves,\nonly one needs the push *immediately* reflected.  All of them have to\nsend to a specific \"backup\" server sometime at night so that's like an\nextra slave, though developers are not expected to hit it so it\ndoesn't need any authorisation information..\n\nSome have enough developers that for convenience reasons they would\nlike to have the developer push to the (local) slave and have the\nslave internally redirect the push to the real master, without the\ndeveloper having to know where the real master is and having to\nconfigure his push-remote correctly.  For developers who're working on\nmultiple projects, with some of them mastered in one city and some in\nanother, this is great.  (I must warn that this feature is only useful\nwhen all the servers trust each others authentication, because that\ngets done at the slave site where the user hit, and authorisation is\ndone on the real master taking the push).\n\nNote that this does no do exactly what you said, but probably comes\nclose enough in some sense.\n\nSo anyway it's been fun.  We're halfway there, and no problems so far.\n Once this is up and running for a few days I will merge it into pu.\n\nregards\n\nsitaram\n"}]}