Over the weekend I was looking at K3S uses-cases which turned into an Ansible series for the most part. After going through @Jay’s Ansible Series, I started thinking about all the configurations I do for various projects: different distributions, servers, databases, development tools, framework dependencies, radio related projects, multi-arch C++/C/Fortran compilers, libs, tool chains, and the list goes on and on.
I already have a background in the Ansible template engine (JinJa) from working on Django projects as it too uses, or can use, the JinJa Temple Engine. For me, this is when things started to click. I’m well accustomed to structured folders / modules in Python, so the notion of
fell right into place. Now it’s just a matter of learning the syntax for Ansible, and organizing things to be the most efficient during roll-outs and subsequent updates.
Anyway, if you do any kind of repetitive installation/configuration, the Ansible Series is a “Must Watch”, even if you only do minor things such as update your disto to the latest patch level.