|
|
Smart modification of httpd.conf for easier updating
So does that mean that ALL the .conf files in /etc/httpd/users will be read by Apache?
I assumed - since there was only a tve.conf file in that directory - that these files was meant to affect the personal sites, the one each user have in http://localhost/~UserName Now it looks to me like:
/etc/httpd/users/User-1.conf affects http://localhost/~User-1/
/etc/httpd/users/User-2.conf affects http://localhost/~User-2/
/etc/httpd/users/BlaBla.conf affects http://localhost/
Is that it???
Smart modification of httpd.conf for easier updating
I don't think that anything in httpd is smart enough to discern what conf file should go with what user by the filename of the config file. I may be wrong, and I am definitely no expert on httpd.conf files. I suspect though that its whats inside the conf files themselves that will determine which dir is served, and therefore which user's site is configured with that file.
Smart modification of httpd.conf for easier updating
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: |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|