You'll also need to set the :runner variable, which specifies who
sudo will try to run the command as. If, on the other hand, you don't
want that command to use sudo, you'll need to set :use_sudo to false.
set :runner, "root" # sudo to root
or
set :use_sudo, false # disable sudo
- Jamis
On May 18, 2007, at 7:25 AM, MuppetMaster wrote:
>
> I have been somewhat successful in at least getting the first stages
> of a deployment going, but am struggling to find specific information
> on what users Capistrano is really looking to have exist on the target
> host. Further, I have yet to find one location with all the possible
> config parameters available in deploy.rb.
>
> What I have is this in deploy.rb for specific users:
>
> ===
> set :rails_env, "production"
> set :deploy_to, "/opt/rails/#{application}"
> set :user, "myu"
> set :svn_username, "myu"
> set(:svn_password) { Capistrano::CLI.password_prompt("Subversion
> password: ") }
> ===
>
> And all is fine until I get here where it is still looking for an
> 'app' user:
>
> ===
> command "sudo -u app sh -c 'cd /opt/rails/nightbell_webui/current &&
> nohup script/spin'" failed on myhost.net
> ===
>
> How do I go about modifying this default user, and exactly what rights
> should my user have to a good secure environ? Best practices?
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
