3 ms·
Somewhat related, I've been fond of flat-file or file-based configs as well. Such as Nagios/Icinga has configuration files, but now seem to suggest a database &
by rob-olmos 6y ago
Somewhat related, I've been fond of flat-file or file-based configs as well. Such as Nagios/Icinga has configuration files, but now seem to suggest a database & UI/API.
File-based config made scripting the generation of the configs pretty easy and updating for changes by just overwriting the files and reloading the daemon.
IIRC, similarly TWiki also uses individual files for the pages and configs with RCS (Revision Control System) per-file to track changes.
- xorcist 6y agoEspecially since Puppet/Salt/Ansible does that part for you. Apply the "web server" class to a node and there is nothing to forget as the relevant config templates are applied both to the monitoring system, the backup runner, and anything else. Configurations that live in a database somewhere is much harder to manage as they have to be set by a config running which needs to be written and maintained.