29 May
2010
29 May
'10
4:42 a.m.
John Dennis wrote:
Hmm... we just had a discussion about how loading every configuration file in a directory trips folks up. Yet another example :-)
We need a solution that is (a) easy, and (b) doesn't involve a massive re-name of files in the middle of a stable release? Even Apache reads the entire directory: ... # Include the virtual host configurations: Include /etc/apache2/sites-enabled/ ... So what's the solution? Why isn't this a problem for Apache, and is a problem here? Alan DeKok.