The typical procedure before touching httpd.conf is to make a back up. If you blow it, you can immediately regress to the back up and you are good to go. I recently had some "hacking" by one of our team who thinks he's competent so, and he generally is, but VirtualMin is not a place to just "try this on for size" anyway, he managed to wipe the directives for one of our sites port 80. We quickly copied the directives for the same domain port 443 and pasted and just changed the port to 80 and the main site come back on line ! Oh boy.. I lost some custom settings in the port 80 directive we also have an anamoly now where Virtual Min shows the aliases for this site, in the left column, but they are not actually present in the directives. (they appear under the VirtualMin pull down menu but all the lines:
ServerAlias *.org
ServerAlias *2.org
are missing in the directives for this site in httpd.conf
but they still work.. because of DNS no doubt... but I should probably add them back in. I guess Virtual Min is reading the domains directory where a dummy folder is made for each of these aliases.
At any rate. so much for my woes... nothing too serious. But it would have been nice if he had made a back up first and we could have regressed and saved ourselves some grief.
Aside from giving me a lecture about "best practices" which I've already sent out to our team (I morphed into a server admin policeman curmudgeon for a few hours!) is there a way to enforce this inside virtualMin: make back up before changing config?
Comments
-