I thought I had got all of that set up. It's the <path to repository>
part that doesn't seem to work.
I've tried using the shared drive approach as well. That gives me a
different set of issues. The command to clone the repository gives:
$ git clone ~/projects/collection collection.git
Cloning into collection.git...
fatal: failed to copy file to 'collection.git/.git/objects/
01/6af769a8dc36e8613d8405ff361e3678358b1a': Operation not permitted
I can, logged in as the same user, create a file in the shared folder.
But git can't for some reason. Does git have a log file that might
give me more information?
On Jan 1, 10:30 pm, Chris Stone <nightshade1...@gmail.com> wrote:
> You would need to have the git installed on the NAS and the git daemon
> configured for ssh. You would then have to setup the NAS repository as a
> remote in your local git repository so you can git push your changes to the
> Assuming git is configured on the NAS I would do something like this
> On NAS
> git init --bare <path to repository>
> On Local Machine
> In project directory
> git remote add origin <path to remote repository> <-- this would be your
> ssh path
> then you can make a "Backup" by running
> git push origin <branch name>
> There are a number of articles on how to run a git server. This is
> basically what you are wanting to set up with ssh access.
> On Sun, Jan 1, 2012 at 3:11 PM, Newt <new...@blueyonder.co.uk> wrote:
> > I don't need to check the repository out, just have a copy on my NAS
> > for safe keeping.
> > I can do it using a network drive, but that just feels a bit wrong.
> > I'm sure SSH should work, but I can work out why.
> > I may fall back to using the network drive if there is no other
> > advice.
> > Cheers.
> > N.
> > On Jan 1, 7:45 pm, Chris Stone <nightshade1...@gmail.com> wrote:
> > > If the network drive is mounted under projects you should be able to git
> > > clone <path to local repo> <folder name you want report cloned into> if
> > you
> > > leave the second folder out it will default to report name. Also the
> > --bare
> > > Camden opt will not check out a working copy it will transfer the
> > contents
> > > of the .git folder to the network drive
> > > Hope this helps with your issue
> > > On Jan 1, 2012 12:32 PM, "Newt" <new...@blueyonder.co.uk> 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 post to this group, send email to firstname.lastname@example.org.
> > To unsubscribe from this group, send email to
> > git-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at