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
While workarounds exist to get private keys to work for authenticating with git (using GIT_SSH env variable and a shell script), building support for this into BigTuna would make it much easier for people to use BigTuna with git. It will also enable people to use BigTuna on environments where they don't control the environment as readily, like Heroku.
[This is a new feature I am already working on, adding it here for visibility.]
The text was updated successfully, but these errors were encountered:
Yes, Heroku being the prime example, but even on EngineYard the key configuration is somewhat strange - they do not put the private key in the standard place or add it using "ssh-add". This is where I first learned about the GIT_SSH trick.
While workarounds exist to get private keys to work for authenticating with git (using GIT_SSH env variable and a shell script), building support for this into BigTuna would make it much easier for people to use BigTuna with git. It will also enable people to use BigTuna on environments where they don't control the environment as readily, like Heroku.
[This is a new feature I am already working on, adding it here for visibility.]
The text was updated successfully, but these errors were encountered: