[git-users] Re: Remote Repositrories

2012-01-12 Thread tombert
What you are trying to do is cloning TO a remote repository.
 "git clone --bare ./cal2 ssh:///volume1/depot/cal2.git"
I don't think that works ... however the "normal" approach is to clone FROM 
a remote repository.
 
So first init the repo on your NAS, then clone to your local directory. 
This way you can save yourself the setup with the remote origin etc.
Also when you clone from remote be aware of the full syntax when using ssh:
"git clone --bare @:/your/remote/folder/repo.git"
 
If your NAS is locally mounted then you can ommit the  and .
 

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/AzA5kMhg3FcJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Remote Repositrories

2012-01-01 Thread Newt
I thought I had got all of that set up. It's the 
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?

Regards,

N.

On Jan 1, 10:30 pm, Chris Stone  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
> "backup"
>
> Assuming git is configured on the NAS I would do something like this
>
> On NAS
> git init --bare 
>
> On Local Machine
>
> In project directory
> git remote add origin  <-- this would be your
> ssh path
>
> then you can make a "Backup" by running
> git push origin 
>
> 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  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  wrote:
> > > If the network drive is mounted under projects you should be able to git
> > > clone   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"  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:///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 git-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > git-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/git-users?hl=en.

-- 
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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] Re: Remote Repositrories

2012-01-01 Thread Chris Stone
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
"backup"

Assuming git is configured on the NAS I would do something like this

On NAS
git init --bare 

On Local Machine

In project directory
git remote add origin  <-- this would be your
ssh path

then you can make a "Backup" by running
git push origin 

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  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  wrote:
> > If the network drive is mounted under projects you should be able to git
> > clone   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"  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:///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 git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>
>

-- 
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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Remote Repositrories

2012-01-01 Thread Newt
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  wrote:
> If the network drive is mounted under projects you should be able to git
> clone   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"  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:///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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.