From: Shawn O. Pearce Date: Fri, 26 Sep 2008 15:39:03 GMT Subject: Re: Internal, corporate, shared hosting solutions Message-ID: <20080926153903.GC17584@spearce.org> In-Reply-To: <8B29890D-C03B-4ECE-9BEF-0A8E8EF7233E@netspot.com.au> Tom Lanyon wrote: > We have some pretty basic requirements: > - authentication and authorisation; some repos are only readable/ > writable by specific people > - accessible; many dev servers are on private subnets, ideally we need > to be able to proxy git access > - not too much messing with unix user accounts on the central git host > (because they're tied to LDAP, for example) Use git over ssh, but use gitosis on the server side: http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way Have each developer supply their own SSH public key, install it into the gitosis database, and they can only read/write repos they have access to in the admin database. Secure, fast, yea, you can actually pick two out of two. :) -- Shawn.