Show HN: Split your ssh_config into separate files
1–5 of 5 posts
Re: Show HN: Split your ssh_config into separate files
#2I've been using it for a couple of years and I really love it.
It's a simple tool, no fancy features, but it gets the job done really well.
For people who work on multiple projects and want to organize their ssh config, this is a must have.
Re: Show HN: Split your ssh_config into separate files
#3I've been using it for a couple of years and I really love it. It's a simple tool, no fancy features, but it gets the job done really well. For people who work on multiple projects and want to organize their ssh config, this is a must have.
Seems like a lot to set up, especially since all you really need is "cat ~/.ssh/config.d/* > ~/.ssh/config"
Re: Show HN: Split your ssh_config into separate files
#4I've been using it for a couple of years and I really love it. It's a simple tool, no fancy features, but it gets the job done really well. For people who work on multiple projects and want to organize their ssh config, this is a must have.
Seems like a lot to set up, especially since all you really need is "cat ~/.ssh/config.d/* > ~/.ssh/config"
Yes, I've done the same thing with a Makefile.
The editing part of "poet" looks good, but it seems like one of those tools that might suffer from being overly developed.
Re: Show HN: Split your ssh_config into separate files
#5I've been using it for a couple of years and I really love it. It's a simple tool, no fancy features, but it gets the job done really well. For people who work on multiple projects and want to organize their ssh config, this is a must have.
Seems like a lot to set up, especially since all you really need is "cat ~/.ssh/config.d/* > ~/.ssh/config"
OP here.
If you already have a working Ruby environment, it's not a lot. If you have to start by installing Ruby, then yes, don't bother.
BTW, this does more than "cat", it supports editing and toggling parts of your config (using --include on files that would normally be excluded).
This was my original use case: Switching between setups for remote and office work.