21–30 of 112 posts
For me you can't beat the combination of Alfred [0] and the SSH workflow [1]. [0] http://alfredapp.com [1] https://github.com/isometry/alfredworkflows/tree/master/net....
Nice job, for me it can't beat a ~/.ssh/config entry though. I wonder why it's not reading ~/.ssh/config btw, should be doable.
Nice job, for me it can't beat a ~/.ssh/config entry though. I wonder why it's not reading ~/.ssh/config btw, should be doable.
They said the purpose of using a .json file was so that your configuration could be synced by dropbox or some other cloud service. I would NOT put my .ssh with all my private keys on dropbox.
What is that cool shell prompt that's in the video?
Nice job, for me it can't beat a ~/.ssh/config entry though. I wonder why it's not reading ~/.ssh/config btw, should be doable.
Earlier quoted context omitted.
They said the purpose of using a .json file was so that your configuration could be synced by dropbox or some other cloud service. I would NOT put my .ssh with all my private keys on dropbox.
You could just make ~/.ssh/config a symlink to your config file in your dropbox folder. No need to put private keys on dropbox.
Symlink'ing a ssh config file with Dropbox was the best decision I've made in a long time.
Same config file no matter which PC I am using, and you can always look up the IP/Hostname and which key it uses (don't store keys on dropbox for "critical" systems) through the dropbox web interface.
For me you can't beat the combination of Alfred [0] and the SSH workflow [1]. [0] http://alfredapp.com [1] https://github.com/isometry/alfredworkflows/tree/master/net....
* Alfred for '>' command * an alias for each server. * Autologin using ssh keys.