Re: Unable to get "pretty" URL aliases working

From: Adam Nielsen <adam.nielsen@uq.edu.au>
Date: Jan 11, 2010, 23:23 UTC
Message-ID: <4B4BB2DC.4090203@uq.edu.au>
In-Reply-To: <7v7hrpvzqa.fsf@alter.siamese.dyndns.org>

Hi all,

Thanks for the replies!

Show 6 quoted lines

> In any case, "attempting to learn Git" doesn't mix well with use of
> "insteadOf" to me.  If you know /path/to/repos/project.git is what you
> want to access, any "attempting to learn Git" person would do more
> straight-forward "git clone ssh://myserver/path/to/repos/project.git", or
> "git clone myserver:/path/to/repos/project.git" which is even better (it
> is shorter to type and is a more natural form to spell ssh transport).

Jumping in the deep end is a valid method of learning :-) Does that mean anyone using my repositories really needs to know exactly where on the server I choose to keep them? Something like "git clone myserver:/mnt/raid/nightly-backedup/public/repositories/git/project.git" isn't particularly friendly. (It's something that bugs me with NFS as well.) What happens if I want to move the repositories to another area on the server? Do all users have to update their local copies with a new origin address?

Is there any hacky way that this could be made to work? I guess I could symlink my repository directory to /git, then myserver:/git/project.git might work.

What actually happens when you use the ssh:// style connection? git-daemon has a --base-path option which solves this issue for git:// URLs, so do ssh:// URLs not use the git protocol at all? What is git+ssh://? Does that SSH to the machine and then connect to git-daemon via localhost? Because that would presumably make use of --base-path.

Thanks again, Adam.