It would be the same if its local or remote you still have to setup
ssh keys so that the user has access to ssh to localhost without
password

So if its the same user to deploy/run cap just add your pub key to
your own .ssh/authorized_keys file...

When this is done you should be able todo this ssh localhost and get
no password

the command to generate the keys is ssh-keygen -t dsa then enter enter

you should now have a directory in ~/.ssh with a key file and the
public key... add the pub key to a file ~/.ssh/authorized_keys set the
permission to 600 (chmod 600 ~/.ssh/authorized_keys) then do ssh
localhost

On Jun 17, 1:09 pm, Mike C <[email protected]> wrote:
> Anyone have any ideas?
>
> On Jun 17, 2:42 am, Mike C <[email protected]> wrote:
>
>
>
> > But the deployment server and the git repository are the same server
> > in my case. What should I do?
>
> > On Jun 17, 1:47 am, Andrew Porter <[email protected]> wrote:
>
> > > Mike C wrote:
> > > > Er well it worked but it still asks for a password. You see, for doing
> > > > git push it used to ask for a password but it doesn't anymore, and
> > > > using cap deploy:update_code used to ask for the password 3 times but
> > > > now it only asks for it once.
>
> > > There are two separate things going on.  cap remotely ssh's on to the
> > > remote server - ssh keys can prevent requiring entering a password here
> > > - and then on the remote machine cap accesses your git repository.
>
> > > If you have told cap to access it as ssh:// etc.. then a password is
> > > required for this also - so you need ssh shared keys between the
> > > deployment server and the git repository.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to