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

Re: Tip: avoiding net overhead using git over sshfs

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Oct 23, 2008, 09:00 UTC
Message-ID
<vpqprlru1na.fsf@bauges.imag.fr>
In-Reply-To
<a2075f4c0810221826w511a3b87r6fea4fb0dee24e1f@mail.gmail.com>
"Felipe Carvalho Oliveira" <felipekde@gmail.com> writes:
Show 11 quoted lines
> 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.
>
> # 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

I think you'd better work locally, and push to the sshfs directory from time to time. Then, you'd both have working tree and .git locally and fast, while keeping the safety of replicating to your ssh server.

-- 
Matthieu
Previous: Johannes Sixt
Message 5 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.