31–40 of 112 posts
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.
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....
You should probably add some install instruction for the workflow, because I have no idea where to start.
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.
"... it makes it easy to generate a dynamic list of hosts from your hosting provider (if they have an API), so you're always up-to-date." It should at least provide a mapping from the json to ~/.ssh/config formats.
Why would I want to touch the mouse?
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.
https://gist.github.com/oogali/5975670
Tab completion for scp/sftp/ssh based on my ~/.ssh/config.
I have two-byte aliases for ssh to all of the hosts I use commonly, doesn't everyone? (It even reattaches my remote screen session.) Why would I want to touch the mouse?
Is it for me? I'll try it, but I don't think so. But I think it serves a need for some people, and I can always get behind ideas that serve or improve--successful or not--workflow/dev needs.
Great work Trevor!
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....
Or (in Alfred) just type: >ssh [host] If you keep your ~/.ssh/config up to date and can remember your host names, I find it quicker to do that than bothering with the workflow.