Skip to content
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

Support for multiple hosts in ssh config and / or ignore ssh config file. #49

Closed
mafredri opened this issue Jul 21, 2013 · 5 comments
Closed

Comments

@mafredri
Copy link

Only the first host is picked out of a line with multiple hosts in the ssh config.

For example:

Host test.google.com secret.google.com

Only test.google.com would be visible.

I would also like to order some of my servers in ssh config into sub menus, and to be able to do this you would either need to ignore the ssh config or provide some syntax in ssh config that creates submenus in shuttle.

@maryisdead
Copy link

+1

I have some hosts in my config that I don't access that often or not with the terminal. I'd like to get rid of those.

@fitztrev
Copy link
Owner

It's not documented yet, but if you prefix the Host in your .ssh/config with a dot, it will be ignored when building the menu.

Also, you can group menu items in your .ssh/config with a "/".

I acknowledge the other issue you mentioned of having multiple hosts per line, though. I'll have to figure out the best way to handle that.

@maryisdead
Copy link

Might be a dumb question, but: Are there no side-effects when prefixing hosts with a dot?

I have something like this in my config:

Host coolhostname.com
HostName coolhostname.com
Port 50008

Prefixing the Host value with a dot makes ssh root@coolhostname.com not acknowledge that section anymore.

Do I have a fundamentally wrong understanding of the whole SSH config thing?

@mafredri
Copy link
Author

Ah, thanks, interesting hidden features, however one limitation I can easily think of with the dot prefix is the following:

Host server1 server2
    HostName %h.website.com

Prefixing server1 with a dot would make it ".server1.website.com" which should not work? Or is the dot prefix something part of the ssh_config and does something special?

Update: Realized I could just work around this by adding e.g. ".disabled" in front of server1 :)

@fitztrev
Copy link
Owner

fitztrev commented Mar 3, 2015

Closing this issue for now. Please open a new one if the issue has not been resolved.

@fitztrev fitztrev closed this as completed Mar 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants