fucking_shell_scripts

Oh there’s this great thing called files. You put your config in there and then you can copy them anywhere, even between AWS accounts. They’re even cloud agnostic so when you move to GCP they still work. Files work great with fucking shell scripts, entirely compatible, it’s rumored that shell scripts beneath the hood are also files. https://github.com/brandonhilkert/fucking_shell_scripts You can use FSS on docker, kubernetes, bare metal (otherwise known as computers), Windows, Mac, Amiga, VMS etc. Plan9 which was made by the creators of Go works exceptionally well with files. Some people even say that AWS converts your LB config object to a config file for nginx when it’s provisioned. If you want to get really crazy you can put all your files in one dir like /etc and then you can use this program grep to search all your configs at once. Y

That stuff isn't readable. It's mostly garbage. If you don't need to make 20,000 devs work together in a chain gang, why even bother? Here's the platforms you need if you're not 20,000 strong: https://motherfuckingwebsite.com/ http://programming-motherfucker.com/ https://github.com/brandonhilkert/fucking_shell_scripts http://vanilla-js.com/

Reminds me of https://github.com/brandonhilkert/fucking_shell_scripts/blob...

Ah yes. The perennial problem of managing system state with anything other than shell scripts. Many variations have been tried. Most end up being some kind of yaml based format or a custom DSL with inscrutable error messages. I don't think the answer is yet another variation on the same theme. The design space for such tools is pretty well trodden and they are all lacking in one way or another. This blog post does not say what exactly about ansible needs to be fixed and what their plan of attack is. It just sounds like the author would like a more responsive set of developers which is a social problem more than a technical one and writing yet another configuration management tool is not the right solution to that problem. Some interesting variations on that theme are http://babushka.me/, http://larsyencken.github.io/marelle/, https://gith

I found Waffles (https://github.com/wffls/waffles) after an extensive search & comparison of Software Configuration Management for my Raspberry Pi projects and CHiP/PocketCHiP commuters. Waffles adheres to what I call "Stupid Simple" as K.I.S.S. implies a complexity challenge. It's so perfectly sized, it would work nearly any embedded Linux system that can run Bash or even an Enterprise size environment. And, don't forget, because it's truly Shell Scripts, you can run it on any architecture Bash is compiled on. Need to distribute your waffle across hosts? Easy, your choices are: git (or ilk), rsync, scp, nfs export, and more - what works on your network to transfer files. The author's blog post walks the reader through their process of simplifying their waffles solution as SCMs like Puppet, Chef, SaltStack, Ansible and others are simply T

Which design flaws are you referring to? As a recent Salt convert (and Puppet expert), I was perplexed as to why such a nice tool would have a man page 40x longer than bash. Turns out it includes extensive documentation for all states supported by Salt, generated from the online documentation. Compare this to the Puppet manual: $ man puppet PUPPET(8) Puppet manual PUPPET(8) NAME puppet See ´puppet help´ for help on available puppet subcommands Obviously no-one will be using everything that Salt supports, so it would be nice if it was broken into sub-sections. But I much prefer having all documentation available in a manual to looping through every module and run "rdoc" as in the Puppet case. Any sufficiently popular configuration management tool will have equally long doc

This reminds me of fucking_shell_scripts[1] but this looks a lot simpler and less angry. I love the idea of truly having no dependencies, since I thought f_s_s was actually written in Bash but turns out to be written in Ruby. BashBooster on the other hand just relies on Bash (no gems, no Ruby) and looks easy to set up. I will definitely be trying it out. [1]: https://github.com/brandonhilkert/fucking_shell_scripts EDIT: BashBooster says it's developed to be used with Vagrant, whereas f_s_s is stand-alone. So it doesn't quite require nothing.