-
Notifications
You must be signed in to change notification settings - Fork 391
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
Is there really a need for a shuttle.json ? #14
Comments
+1 .ssh/config is already ok http://nerderati.com/2011/03/simplify-your-life-with-an-ssh-config-file/ and duplication is a risk. (but i understand json parsing is easier) |
I did a quick search and couldn't find anything about it -- maybe one of you can answer it, but can the SSH config file do what the json file does for organizing into submenus? |
yes, look at the Host part Host namespace-server1 |
Well, there is no built-in hierarchy in ssh config that I know of, however @grigio's solution could work if you group by Not-so-great thing about this solution is that you would have to use the 'fully qualified' host alias when ssh'ing manually but if this tool works nicely enough, you shouldn't have to. :) |
👍 for this feature. Actually, I don't really see the point of such an app without .ssh/config support. I mean: I always have iTerm2 open and all I have to do to is type 'ssh ' in, press tab to list my configured hosts and press enter to connect to the selected one. Why would anybody with a great .ssh/config file will want to use this app if he have to manually rewrite all his settings in a non-standard json file? |
@fitztrev what do you mean with "..a friendlier name to appear.." ? I tried with my sshconfig and Host can have dots and / . So using this convention there shouldn't be limitations.
Which could be rendered as:
and of course you're still able to access to that website with:
What do you think of this Unix-y convention over configuration? |
👍 for automatic parsing of the ssh config file. By the way the |
@grigio I meant allowing for the label to be "My Awesome Host" instead of "myawesomehost.com", like the current JSON configuration allows. But now that I think about, I don't see that as necessary. I do really like your proposal. I think that's a good way to go. It would probably also add support for 10.6 as a byproduct. |
@fitztrev space isn't allowed as Host character, but you could do:
but I like more to have the Host as The unique thing to parse is the row which starts with "Host .." and split('/') to build the data structure with "namespace" and "HostName". I'd open a pull request if I'd know objective-c :) |
already configured in the ssh config file. Currently namespaces identified with "/" are supported with one level of nesting. Let's discuss.
The current PR supports nesting for SSH Config Values. |
👍 |
Released in v1.1.0. |
I tried to delete my .shuttle.json and now i get "Error parsing config". I've the same error also with the default one |
Why not use ~/.ssh/config to generate hosts and other ssh options (including username + password or specific identify file, etc.)?
And I know next-to-nothing about Objective C and Apple Dev, but I would also suggest looking for the proper "terminal" app using something like LaunchServices if possible.
The text was updated successfully, but these errors were encountered: