|
|
|
|
|
|
by roel_v
5381 days ago
|
|
|
"I am quite happy editing them with vi or emacs" Sure, so am I (well except for Sendmail configs). We were talking about programmatically editing here. "And, when I wanted to parse my own config files, I always had libraries to do it ready." Really? How do you, in bash, write a script to change, or if necessary add, an 'IndexAllowed' directive to a certain specific VirtualHost? Mind you, Apache config files can Include other files (and many distros ship with default config files that use this). "Are you trying to build a GUI tool to edit Apache configuration files?" I'm not building anything, I was just using this as an example of things you'd want to script, for example in the context of a web hosting provider who wants to automate the creation of new customer setups. (Yes I realize that there are many way to attack this specific problem, but most of them are very specific to Apache and would have to be re-engineered for each problem) |
|
|
I am not sure it's a good idea. Just generating the files from a CMDB and placing them in the servers seems the simplest approach. I do it. This way I have the nice side effect that anything a sysadmin did directly and manually on the server bypassing the config database (something that shouldn't really be done) gets wiped out as soon as possible.
> in bash
Almost every Unix out there has Python, Perl and Ruby already installed. You don't need to use bash unless you really want it.