5 ms·
I'd be happy if their was just a decent linter for all configuration files. My test process right now is to spin up a vm and test something like an nginx reload
by ben_jones 10y ago
I'd be happy if their was just a decent linter for all configuration files. My test process right now is to spin up a vm and test something like an nginx reload or an ansible-playbook, then if it passes apply it to a distributed testing environment and then if it passes consider applying it to production.
This seems crazy to me when intelli-sense for many languages can seemingly read my mind but configuration is in many ways still a trial and error process..
Does anyone know of ways to parse many of the common configuration file formats? From linting to code completion to best practice (or worst practice) checks. IF not and somebody wants my money yesterday, theirs your startup.
- jacobbudin 10y agoIf you have nginx installed, you can test nginx configurations like so: $ nginx -t -c <configuration file>
- icebraining 10y agoAnsible also has --syntax-check and even --check, which "tries to predict some of the changes that may occur".
- ben_jones 10y agoI still have to spin up the vm though to make sure changes to things like proxy settings won't affect me further down the stack. But thanks for the tip!