You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2024. It is now read-only.
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...
The text was updated successfully, but these errors were encountered:
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.
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 thebundle install
step means that the connection to the SSH agent is gone. Anyway, the end result is that bundler can't auth andcap deploy:setup
fails...The text was updated successfully, but these errors were encountered: