4 ms·
For me the problem with configuration is not the config files - but getting the config into the running application. There is never a perfect way - it is a ch
by lifeisstillgood 13y ago
For me the problem with configuration is not the config files - but getting the config into the running application. There is never a perfect way - it is a chicken and egg situation - pass it in from the command line? Ok now do that for 100 servers, I know let's have an app - but that needs to know which 100, for which we write a config file ...
it's all doable, but I always think I could make a better choice.
- hugofirth 13y agoInteresting - so would you be looking for some kind of centralised configuration deployment system?
- emmelaich 13y agoAugeas plus ssh (ansible, whatever) plus some special sauce will do it for you mostly.
- icebraining 13y agoAs an amateur sysadmin, I'm curious - why use Augeas instead of having a template of each config file be filled in and copied to each node?
- phaer 13y agoAugeas provides some abstraction over different config formats so you don't even have to know the syntax and are less likely to make typos.
- lifeisstillgood 13y agoNo. I am just moaning on the Internet. To be clear, I am occasionally frustrated by the Chicken and Egg nature of configuration, when there is always another layer of abstraction to start with. So how do I deploy my saltstack servers so that I can pass them the config so that they can ... a recent example - you start a script / daemon running with a arg pointing to a config file. But that config file might fail and I cannot log that it failed cos the log location is in the config file. There are half a dozen solutions but it just annoys me.
- anton_gogolev 13y agoUm... Puppet/Chef/Ansible/CFEngine/Bcfg?
- barrkel 13y agoYes, and Puppet etc. has its own configuration format (typically Hiera for Puppet), and now you need to configure your configuration (typically with erb or puppetlabs-concat). Most of your fancy configuration format features are wasted.