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

Re: Tip: avoiding net overhead using git over sshfs

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Oct 23, 2008, 08:32 UTC
Message-ID
<490036A2.20608@drmicha.warpmail.net>
In-Reply-To
<a2075f4c0810221826w511a3b87r6fea4fb0dee24e1f@mail.gmail.com>
Felipe Carvalho Oliveira venit, vidit, dixit 23.10.2008 03:26:
> Use git over sshfs is not so good, but is an option for people that
> don't have shell acess to the server/hosting like me.

I'm sorry but I'm afraid I'm missing the point: If you don't have shell access then you can't use ssh(fs), can you? Maybe you mean you can't set up git daemon or gitweb.cgi on the server?

Show 13 quoted lines
> # mounting
> sshfs -o workaround=rename <user>@<host>:/home/<user>/  <mount_point>
> cd <the_directory_of_your_project>
> 
> # we will move the .git directory to the local filesystem
> mv .git ~/.my_project_git
> # and create a symlink to the local .git
> ln -s ~/.my_project_git .git
> 
> Done!
> 
> Now you can open gitk instantly ;-) and don't need to have the entire
> .git thing on a remote filesystem.

In fact your complete git repository is now on the local filesystem, with only the worktree checked out on sshfs. Is that what you are trying to achieve? Or do you want to "synchronize" repos on local and sshfs filesystems?

Michael
Previous: Felipe Carvalho OliveiraNext: Felipe Carvalho Oliveira
Message 2 of 5 in “Tip: avoiding net overhead using git over sshfs”
  1. Felipe Carvalho OliveiraOct 23, 2008
  2. Michael J GruberOct 23, 2008
  3. Felipe Carvalho OliveiraOct 23, 2008
  4. Johannes SixtOct 23, 2008
  5. Matthieu MoyOct 23, 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.