-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Agent Forwarding #23
Comments
Opened an internal discussion in Trello: https://trello.com/c/FH7nfY41 I'll update this issue when there's progress. Thanks. |
Excellent, thanks! |
Until a more convenient solution is implemented, you can easily achieve this by simply appending or prepending '-A' to another option
or even
should work. +1 for a future
|
Nice one. Didn't even think of that. Tried it and works perfectly. I'll use this until an |
+1 for a SSH Agent Forwarding is almost always what I want when deploying, unless other people deploy radically differently regularly |
Scheduled for v0.2.1. |
Hi Nadarei,
Agent Forwarding is probably one of the more appealing features of Capistrano. With this option enabled, you won't get this error because it allows you to use your local ssh keys. Normally, like in this case, you have to log in to your server, generate a new SSH key and apply that SSH key to for example Github. Then, this command would work. However with Agent Forwarding you do not need to do that and you can simply use your own local machine's SSH key instead.
See:
It would be great if Mina could also support this feature as it's always pain to add a new key to GitHub for every single server you want to hook up to it.
Note that I looked around and didn't find the option, but if I overlooked something please let me know.
Cheers,
Michael
The text was updated successfully, but these errors were encountered: