MisterTea
ET support for config file
ET has some specific options which are not overlapping with SSH (like -jport, -x` etc.). It would be great if those could be pulled from a configuration file just like SSH does it (not the same file SSH uses though), so users don't need to create aliases. It would definitely improve tool automation and make the configuration deployment easier.
Since most people only need to rerun et when their client reboots, this is a low-pri issue. Can you use a bash script that takes the server as a parameter and sets the appropriate switches?
Sorry to see this closed. I would have preferred to either see it get tagged low priority or added to a distant future milestone. Sorry, but closing an issue to me is either saying it is a) resolved or b) won't fix, of which I am assuming the latter is meant.
I have servers that are in places where the requirement that non-default ports be used for forwarded services, which means I need to add the port to the command when connecting.
One of the main reason I started using et after using mosh is that et has port forwarding but mosh does not. Without this I have to remember which ports I want forwarded for each host.
Yes, it is possible to write a shell script with a case statement that would run the commands I want for each host I want to connect to, but the simplicity of having a configuration file like ~/.ssh/config for et would be a very nice feature to have.
Also not sure if I buy into the "only need to rerun et when their client reboots", I don't stay in an eternal connection to servers and end the connections when I am done working.
Hey, thanks for the feedback.
I generally close issues after 6 months to keep the issue list clean, but you make a great point. I wonder if there is a way for people to put a bounty on issues like this to inspire the community to build it? As it stands, me and Ailing do 99% of the coding so if we aren't interested, leaving the issue open just clutters the repo. I'll reopen for now.
@MisterTea There are different sites that allow one to issue bounties. Issue Hunt was setup for one opensource project (Boostnote) but was so successful that they opened it up to other open source projects. Here is an interesting article about IssueHunt.