Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Smart modification of httpd.conf for easier updating' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Smart modification of httpd.conf for easier updating
Authored by: extra88 on Jul 07, '03 11:49:37PM

The name of the conf file is irrelevant. The last line of httpd.conf is simply "Include /private/etc/httpd/users." Any files in that users directory (probably even if they don't end in .conf) will be treated just as if they were within the httpd.conf file itself. The user .conf files get their user specificity from their contents. Here's the first line from extra88.conf:
<Directory "/Users/extra88/Sites/">
I could rename it 88extra.conf and it would still do the same thing.

For dropping in other .conf files to the users directory, it might be a good idea to name it such that it will get processed before the real user.conf files (don't forget the alphabetizing will be case sensitive).

Unfortunately, none of this answers the question of whether you can get away with adding or enabling modules in an "Included" conf file.



[ Reply to This | # ]