I have done something similar. What I then did in my working directory was:
git remote add remote ssh://user@host//path
I can thereafter do a:
git push remote
to push out all changes to the remote. You could even do two git push
commands. The first into the "local" repository. The second into the
The main difference, for me, was that I "primed" the "remote" by doing an
ssh into the my server upon which the NAS is NFS mounted. I did:
git --bare init
to set up the git repo (empty) on the NAS. I then log off of the server,
going back to my desktop. Once there, I "cd" into my project working
directory and do:
git remote add remote ssh://user@server/nfs-nas/path/git/project.git
git push remote --all
The git push copies everything out the "remote" git repository on the NAS,
via the "server".
On Thursday, November 15, 2012 1:05:57 PM UTC-6, iñigo medina wrote:
> I'd create a bare repository from active one and then copy it on remote.
> $ cd ~/projects/repo
> $ git clone --bare .git ../repo.git
> $ cd ../
> $ scp -r repo.git user@host://path
> From there, you could then add such bare repo to your active repo as a
> $git remote add origin ssh://user@host/path
> Of course, you should always have a Git server running on the remote host.
> On Sun, 1 Jan 2012, Newt wrote:
> > Hi,
> > I'm a bit confused with using remote repositories.
> > I've got a local repository set up. I'm now trying to clone it onto a
> > network drive.
> > So locally, I've done:
> > cd ~/projects
> > I've then tried:
> > git clone --bare ./cal2 ssh://<ip address>/volume1/depot/cal2.git
> > However, all this does is create a new folder in ./cal2 called ssh:
> > and then creates directories beneath it. That's not what I want. What
> > am I doing wrong...
> > Cheers,
> > N.
> > --
> > You received this message because you are subscribed to the Google
> Groups "Git for human beings" group.
> > To unsubscribe from this group, send email to
> > For more options, visit this group at