Re: Creating new repos

From: Petr Baudis <pasky@suse.cz>
Date: Oct 27, 2006, 12:39 UTC
Message-ID: <20061027123918.GB20017@pasky.or.cz>
In-Reply-To: <200610271229.k9RCTARu016773@laptop13.inf.utfsm.cl>

Dear diary, on Fri, Oct 27, 2006 at 02:29:10PM CEST, I got a letter where "Horst H. von Brand" <vonbrand@inf.utfsm.cl> said that...

Show 16 quoted lines

> I'm trying to set up git repos for remote access here. I set up git-daemon
> and got it working (some older repositories do work fine), but now:
> 
>   $ mkdir /var/scm/user/SomeRepo.git
>   $ cd /var/scm/user/SomeRepo.git
>   $ git --bare init-db
>   $ touch git-daemon-export-ok
> 
> All OK, but then, from a remote machine:
> 
>   $ git clone git://git-server/user/SomeRepo.git
>   fatal: no matching remote head
>   fetch-pack from 'git://git-server/user/Test.git' failed.
> 
> The empty repo created by init-db should be cloneable, so as to get the ball
> rolling easily.

Well there's really nothing to clone, so it's tough. :-) What would such a clone be supposed to do? It has no branches to record as belonging to origin, and note that Git's git-clone is long-term broken in the sense that it won't pick new branches as they appear in the remote repository. So a clone of an empty repository would be useless anyway.

> You can't push into such an empty repository either.

This is supposed to work. What error do you get?

> Any suggestion of how to set up a server into which users can create their
> own repos /without/ giving out full shell accounts?

Sure:

	http://repo.or.cz/w/repo.git

But it may be quite an overkill for you. ;-)

If you want them to be able to do it over ssh, you would need to provide a trusted tool which would manage the repository setup, that means not only doing init-db, but also managing the export-ok files, description file, you'd likely want to enable the post-update hook (but probably not any other hook or let the user edit it since at that point you've given him full shell access), etc. And the tool would have to be carefully reviewed since it's security-critical.

Show 8 quoted lines

> Also, the behaviour of git-daemon is different when using git or ssh+git,
> you need to give the full path for the later but not the former (given
> --base-path=/var/scm):
> 
>   git://git-server/user/Test.git
>   ssh+git://git-server/var/scm/user/Test.git
> 
> Is this intentional?

git+ssh has nothing to do with git-daemon, it's executing other git commands remotely.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1