> >>> I would still urge to consider bundling a standard 'conf.d' with >>> httpd.conf including sub configurations underneath this location. >> This >>> seems to be common practice across other httpd distributors. So, I >>> wonder why we cannot retain this behavior within SXDE as well. >> I'm still a bit confused on the "conf.d" directory. Is that a >> directory where a user puts their own configurations such as >> >> conf.d/bigserver.conf >> conf.d/http+php.conf >> conf.d/openproject.conf >> > > Yes, you got this right. > > It would be nice, if the default httpd.conf that we ship has a line at the end > > include conf.d/*conf > > This way, customers can add their task specific configuraiton underneath. >
So you mean our installation would provide a new conf.d directory without any .conf files ? I still think user can use "extra" directory for the task specific configurations. Regards, Seema.
