Neil, The existing sudo-based approach seems to work well for most people, but I do understand that it won't be a perfect fit for everyone. I'd have no problems at all if someone wanted to release an alternative deployment module, which either replaces or extends the standard deploy namespace. I'd love to see a working prototype of a deploy system that works as you describe; if it can be made transparent to the user, I'd even consider wrapping it into Capistrano's deploy package itself.
- Jamis On Jun 18, 2007, at 8:41 AM, Neil Wilson wrote: > > One of the things that is annoying about Rails deployment is the need > to use 'root' access to do certain tasks. Capistrano recipes are > liberally sprinkles with 'sudo' requests. > > However on server clusters using public key infrastructure this makes > automatic setup a bit more problematic than it should be. > > I was wondering whether the default 'sudo' commands used in Capistrano > could be translated into setuid scripts and wrapped up in a separate > Gem or package. That way all the standard recipe tasks could be run as > the default user without requiring privilege elevation at all. > > Thoughts? > > NeilW > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
