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

Ssh extension #89

Closed
nean-and-i opened this issue Nov 10, 2015 · 3 comments
Closed

Ssh extension #89

nean-and-i opened this issue Nov 10, 2015 · 3 comments

Comments

@nean-and-i
Copy link

it would be great if albert get a ssh search module, just as like implemented in synapse or quicksilver (osx)
devops will definetly love to have following features implemented:

  • search in existing .ssh/config or/and .ssh/known_hosts and in configurable, additional lists (yml,xml,csv,...)
  • configurable terminal app to start/trigger ssh
  • multiple select to start/trigger multiple ssh sessions (pro++: multiple session in 1 terminal window via tmux or terminal config -> is doing great for broadcast commands simlar to cluster-ssh)
@ManuelSchneid3r
Copy link
Member

ManuelSchneid3r commented Feb 5, 2017

I'd really like to have ssh at my fingertips but somehow its unclear to me how this extension should behave. First Synapse does not show anything for me. Kupfer just list the config entries on ssh so it looks to me as if they had no clear concept of an ssh plugin too.

The known_hosts, hmm, well have you ever checked the file? If you use git over ssh a lot, the contents of this file are useless. The only use case I can imagine is if you have a hard to remember IP that you want to reconnect more often. However this use case may be covered by a selective history similar to the bash reverse search.

The idea of this config entries is to match hosts to attach info if you connect to a host that matches that config entry. They are not necessarily hosts on their own, although most of us use them like that.

Aside that I'd find it cool if I could connect to hosts that are not listed in the config or known hosts as well. And this one makes the whole thing somehow useless because it basically does nothing else but just open a terminal an run the command in the input box...

What do you think?

@ManuelSchneid3r
Copy link
Member

Okay just found out that ssh bash completion list only the hosts containing no wildcard characters {*,?}. Those are good candidates. I think making the known_host optional is a good idea. However I am not sure how to allow both quick connect and the predefined hosts.

@ManuelSchneid3r
Copy link
Member

In v0.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants