On Sat, May 14, 2011 at 1:46 AM, Lee Hambley <[email protected]> wrote: > Tim, > If you use `visudo` it's as easy as doing something like: > Cmnd_Alias DEPLOY_CMDS=/usr/bin/whatever, /usr/sbin/whatever-else >
As I mentioned this was a one off thing. I didn't want to mess with sudo permissions on a permanent basis. Normally I just do "cap production deploy" and everything works great. I had an instance where I wanted to check to see if something was installed on the machines and it meant doing httpd -M to check to see if a particular module was loaded on the web servers and some grep commands to see if some entries were set in the conf files. Since we have multiple web servers I thought "this is a great time to give cap shell a try". I had never used it before so I thought it would be a good learning experience. So it seems to me that someplace in capistrano there is a variable set which determines what capistrano is passing as the root password and I was just wondering how I can set that from the cap shell. I imagined a scenario that went like this. cap shell set sudo_passwrod= "blah" sudo httpd -M sudo grep 'blah" /etc/httpd/conf.d/* And voila I'd be done. I guess that's not possible, I'll have to see if I can hack it to make it happen because it seems like a tremendously useful thing for these one off types of things. -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
