recap
recap copied to clipboard
the bundle install step fails for Gemfiles with Git deps, even though its the same a/c as app
So, my app has a private Github repo gem dependency. The app is also a private Github repo (the same account). Agent forwarding works fine for cloning the app, but (I'm guessing) the su - app-user
launch of the bundle install
step means that the connection to the SSH agent is gone. Anyway, the end result is that bundler can't auth and cap deploy:setup
fails...
Hey Matt, sorry I hadn't noticed this issue - I need to get my github notifications sorted out. This sounds like it's going to be a pain to fix, but I'll have a think about it. I guess that if the deploying user can clone the code, they might be able to install the bundle too.
Just browsing past this - you could try the approach outlined here http://serverfault.com/questions/107187/sudo-su-username-while-keeping-ssh-key-forwarding