There is an easier way than to hack ssh.rb directly... :) You can do this in your deploy.rb:
ssh_options[:forward_agent] = true To change who sudo runs as, set the :runner variable: set :runner, "bob" - Jamis On 7/27/07, mcr <[EMAIL PROTECTED]> wrote: > > On Jul 25, 3:05 am, harm <[EMAIL PROTECTED]> wrote: > > I waited for cap2 to be released before I (re)deployed my app(cap > > deploy:cold). I have a server which is both my svn and deployment > > server. My workstation has a ssh key which needs a password. Using a > > Mac I use SSH Agent to manage that password but I might be possible > > that that does not work properly. But the biggest hitch is the fact > > that I use different usernames. In cap1.4 I could use: set :user, > > I hacked /var/lib/gems/1.8/gems/capistrano-2.0.0/lib/capistrano/ssh.rb > to include > :forward_agent => true, > > This permitted the SVN checkout to get at the repository correctly. > What I don't know is how to determine how the sudo works. > It appears to do: > > sudo -u app ... > > and I think that I'd like to change "app" to the userid on which my > application should run. > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
