I still have question about this whole thing though! :-) Security The process starts by the page being submitted by the apache/www user. How do I securely transfer "power" over to the deployer user? I've been hard-coding the password in to do an su like:
# whoami apache # echo 'PassWord' | su - deployer-user -c "COMMAND HERE" But that means the password is in a file on the system, which bugs me. How can I allow apache/www to execute these scripts in a secure way? There must be a better way? Matt On Aug 13, 2:22 pm, goodieboy <[EMAIL PROTECTED]> wrote: > Sorry for not getting back sooner. I created private/public keys, put > the public one on the server and then put this in my recipe file: > > set :user, 'my-user' > ssh_options[:username] = my-user' > ssh_options[:host_key] = 'ssh-dss' > ssh_options[:paranoid] = false > > Hope that helps! > > Matt > > On Aug 6, 2:33 pm, Jeff <[EMAIL PROTECTED]> wrote: > > > On Aug 1, 9:11 am, goodieboy <[EMAIL PROTECTED]> wrote: > > > > OK answered this myself. This is perfect, using a password-less pass- > > > phrase doesn't require ssh-agent to be running! :) > > > Any chance you could post the code that finally worked for you? > > > Thanks! > > Jeff --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
