On Jun 5, 2007, at 7:02 AM, doron wrote: > thanks for the reply and for creating this tool. > > after reading some other posts i guessed that i would have to do > something like that. > but why is that? is there a good reason for these tasks to not use > "sudo"?
Mostly because I don't believe those tasks need to use sudo. I can see where the setup task _might_ benefit, but update_code and symlink are definitely not sudo operations, if the other directories have been created with the proper permissions. > on the meantime i choose the path of changing permissions in the > before and after hooks. and also putting my user in a certain group > that has more permissions. Sounds good! - Jamis > > > > > On Jun 4, 2:01 am, Jamis Buck <[EMAIL PROTECTED]> wrote: >> You'll need to override (redefine) the task in question, and use >> "sudo" instead of "run". >> >> - Jamis >> >> On Jun 3, 2007, at 7:41 AM, doron wrote: >> >> >> >>> i want a built in task like setup, update_code or symlink to run >>> with >>> sudo. >> >>> how do i do it? > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
