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

Re: Unable to get "pretty" URL aliases working

From
Adam Nielsen <adam.nielsen@uq.edu.au>
Date
Jan 14, 2010, 00:45 UTC
Message-ID
<4B4E6947.2020009@uq.edu.au>
In-Reply-To
<7vockytrwy.fsf@alter.siamese.dyndns.org>
Show 5 quoted lines
>> What actually happens when you use the ssh:// style connection?
> 
> Be it ssh://host/full/path or host:/full/path or host:path/in/home, you
> log in as whatver ssh identifies you as to the server, and start a
> server-side git process over there.

Ah ok, that makes more sense. Strange then if it's a server-side git process that it ignores the server's /etc/gitconfig where aliases can be set up.

Show 5 quoted lines
> With ssh://host/path notation, there is no way to specify any relative
> path (i.e. "/path" part begins at root) so it will mean the same thing for
> everybody (unless you are getting chrooted or something), while host:path
> notation allows relative path which will be taken relative as where you
> are, i.e. home directory of the user on the server.

In that case I symlinked my repository folder to /git so that SSH users can "cd /git/project.git" and this seems to work well. I can now use git URLs like ssh://server/git/project.git even though the repos are buried much deeper down in the tree.

Thanks for the explanations!

Cheers, Adam.

Previous: Junio C Hamano
Message 6 of 6 in “Unable to get "pretty" URL aliases working”
  1. Adam NielsenJan 11, 2010
  2. Johannes SixtJan 11, 2010
  3. Junio C HamanoJan 11, 2010
  4. Adam NielsenJan 11, 2010
  5. Junio C HamanoJan 13, 2010
  6. Adam NielsenJan 14, 2010

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.