Hi, I'm having a bit of problem with the way Capistrano handles the user permissions for deployment.
I have a pretty large amount of ruby apps to maintain and deploy. All the apps run as separate users in a chrooted environment (ex. app1, app2, app3, ...) . Those application users don't have remote access on the production machine, so no ssh access possible. To make it a bit easier for myself, I decided to deploy all those app's as 1 user (ex. deployer). Now running deploy:setup is a breeze. In deploy.rb, user is set to deployer and thanks to use_sudo set to yes and admin_runner set to app1, the capistrano skeleton is build correctly with the correct permissions. But then the biggest problem comes. When you run deploy:check (or anything else for that matter) it fails because the deployer user doesn't have sufficient permissions. I know this is because during those operations, capistrano doesn't make use of "try_sudo" during the execution of commands. But I have no clue how to overcome this without having to rewrite a large portion of the capistrano deploy commands. I don't feel like giving those application users remote access just for deployment purposes. That would mean I have create new keys for every project that needs to get deployed. Also using 1 key for all users is a bit ugly, because when you need to change the key, you'll have to change it for all those users, and I don't really feel like changing keys for +20 users. So hopefully someone can point me to the right direction. It could be that I'm just having a bad perception on deploying the applications. So feel free to comment. -- * 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
