Skip to content
This repository was archived by the owner on Oct 19, 2024. It is now read-only.

the bundle install step fails for Gemfiles with Git deps, even though its the same a/c as app #83

Open
fidothe opened this issue Jul 25, 2013 · 2 comments

Comments

@fidothe
Copy link
Contributor

fidothe commented Jul 25, 2013

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...

@tomafro
Copy link
Owner

tomafro commented Aug 8, 2013

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.

@jeremyolliver
Copy link

Just browsing past this - you could try the approach outlined here http://serverfault.com/questions/107187/sudo-su-username-while-keeping-ssh-key-forwarding

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants