Re: Question around git-shell usage in Everyday Git

From: Linus Torvalds <torvalds@osdl.org>
Date: Feb 1, 2006, 23:37 UTC
Message-ID: <Pine.LNX.4.64.0602011530530.21884@g5.osdl.org>
In-Reply-To: <7vy80u64xf.fsf@assigned-by-dhcp.cox.net>

On Wed, 1 Feb 2006, Junio C Hamano wrote:

Show 6 quoted lines

> 
> Do you mean to reuse single directory /home/gitu/ for user A, B, C,
> and hang repositories /home/gitu/{X,Y,Z} for projects?  I'd
> imagine things could be arranged that way.  User A and B but not
> C may be in "projectX" group and /home/gitu/X is writable only
> by projectX group members and such...

That would work from a _git_ angle, but I don't think that was what Alan was talking about, and it would failr horribly from a "ssh" perspective (because "ssh" will want $HOME/.ssh/authorized_keys etc).

So I _think_ what Alan was describing was just a

	/home/user-A/project.git
		     another-project.git
		     ya-project.git
	      user-B/myproject.git
	      user-C/..

setup, and then people can always just describe their own projects by just doing "git pull host:<projectname>", without ever caring _where_ their home directory is.

(And yes, "git pull user@host:project" also obviously works fine, in case your user name at the hosting site isn't the same as the user name on your local site).

However, to be truly useful for this kind of hosting schenario, "git-shell" still needs to be extended to be able to at a minimum create (and delete) projects.

It probably also makes a lot of sense to be able to pre-populate a project, so that you don't have to do a remote "git push" to push a big project over the network, when another version of that project already exists at the hosting site.

			Linus