Related to deploy:setup. This task uses 'run' instead of 'invoke_command' to create directories. Is there any way to overrule this since the base directory on our servers are by default not writable by the cap user?! I think it can be done with a before/after hack, but I'm wondering what formula is used to determine run or invoke_command usage in the Capistrano base files?
Thanks! -andy On Jul 28, 6:09 pm, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > If you need to execute a command on the remote servers via sudo, you > can use the sudo helper in your tasks: > > task :some_task do > sudo "command" > end > > Running cap itself via sudo will not affect how the commands are > executed on the remote servers. > > - Jamis > > On 7/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Dear list: > > > My first working out of capistrano. > > Some tasks are 'run' and others 'sudo' > > > What is the best way to execute commands where sudo is required? > > If I run 'sudo cap COMMAND', I need a root password. > > Do I have to patch my recipes to sudo instead of run? > > I would prefer to run 'cap sudo COMMAND' to modify my command line > > > I used group permission on /var/www in order to rundeploy:setup, but > > I'm not sure > > that's the best way. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
