> 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
or is it just a rename of the current "extra" directory and largely
stores the configuration files we currently ship from there?
dsc
