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

Re: Tip: avoiding net overhead using git over sshfs

From
Felipe Carvalho Oliveira <felipekde@gmail.com>
Date
Oct 23, 2008, 11:51 UTC
Message-ID
<a2075f4c0810230451lefff6ffnc283f4078eff9f9c@mail.gmail.com>
In-Reply-To
<490036A2.20608@drmicha.warpmail.net>

On Thu, Oct 23, 2008 at 6:32 AM, Michael J Gruber <git@drmicha.warpmail.net> wrote:

> 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?

Yes, i can't set up any git daemon or any other software. I have just sftp acess. And sftp is a "dumb protocol" to use git.

On Thu, Oct 23, 2008 at 7:00 AM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> 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.

I can't use git-push as I explained before. I use git as a deployment tool in this case. I work locallly and use git-pull to sync my local repo and the "production"(server). Git works better than a manual (S)FTP sync.

I hope I'm more clear now.

-- Felipe

Previous: Michael J GruberNext: Johannes Sixt
Message 3 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.