I'm having a problem which I think may be related to the ones mentioned in these other 2 threads: http://groups.google.com/group/capistrano/browse_thread/thread/707ba587b3848abc http://groups.google.com/group/capistrano/browse_thread/thread/dff88affd9c73954
For compliance purposes, I need to have all access to our production servers to be through individual usernames, not generic ones like app and admin. (I should note that I'm using ec2onrails, which is built on top of capistrano and I've already had to do a few fixes there.) I've managed to get things working to where I can do all ssh access via a specific username--took a little fixing to ec2onrails where some usernames were hardcoded. It looks like code deployment is happening under my ssh username, not 'app', so then running the app runs into some problems because of file ownership+protection. At the moment I've worked around this by adding my ssh username to the app and admin (and root) groups. Any recommendations on a better way to handle this? Maybe I just have to override Capistrano::Deploy::Strategy#deploy! as suggested in the other thread? Thanks, dwh --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
