Hi guys, Thanks for your responses. I was not subscribed to email updates on this post, so I never received them. My fault.
We ended up creating a deploy user and adding each developer's/deployer's public key to authorized_keys. This solution is not ideal from a key management standpoint, but it does prevent us from running into directory permissions issues we had in the past (which we had to resolve by prepending sudo to the default shell). I think we will stick with it for the time being. Thanks, Clinton -- -- * 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 --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
