git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Internal, corporate, shared hosting solutions

From
Shawn O. Pearce <spearce@spearce.org>
Date
Sep 26, 2008, 15:39 UTC
Message-ID
<20080926153903.GC17584@spearce.org>
In-Reply-To
<8B29890D-C03B-4ECE-9BEF-0A8E8EF7233E@netspot.com.au>
Tom Lanyon <tom@netspot.com.au> wrote:
Show 7 quoted lines
> 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.
Previous: Tom LanyonNext: Johan Herland
Message 2 of 3 in “Internal, corporate, shared hosting solutions”
  1. Tom LanyonSep 26, 2008
  2. Shawn O. PearceSep 26, 2008
  3. Johan HerlandSep 26, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.