3 ms·
Like most things system, this can be replaced with regular existing tools and a shell script. You will gain a lot more valuable knowledge and experience by lear
by throwawaaarrgh 3y ago
Like most things system, this can be replaced with regular existing tools and a shell script. You will gain a lot more valuable knowledge and experience by learning how to use existing systems, rather than picking up yet another magic unicorn tool that promises you the moon but won't help you when it breaks.
Do you plan to be doing this job for the next 10 years? Then set aside the time to learn system tools and scripting. The time investment, however long it takes, will pay itself off many times over, guaranteed.
- switchbak 3y agoOr, you could use existing tools and patterns so the next person picking up your project has even the slightest chance of being productive. Yes you can glue things together with existing stuff. Let's not pretend that cgroups+namespaces+dnsmasq (or whatever) tech is actually a better solution. It might be "simple" via some metric, but it's yet another ad-hoc piece of engineering that has to be understood and maintained. I've seen this at a former job, and it was an absolutely horrible idea.
- throwawaaarrgh 3y agoSure. But if you're going to use a "real" system that can be adopted by others, you might as well use the most popular, well known, well funded, well supported tool out there. Using this "Capistrano alternative" won't be familiar for people that come after, and they'll spend just as much time learning it as learning a janky shell script, except the janky shell script is at least tailored to your use case.
- switchbak 3y agoI'd agree with that too. I'd be open to something truly simple (Nomad perhaps?) over K8S in some scenarios, but if I'm going to take a gamble, it's going to have to be a lot simpler to provide enough benefit on taking a chance on a less popular piece of tech.