On Sat, Jul 16, 2016 at 07:00:21PM -0700, Michael Lustfield wrote: > Using conf.d/* is a very common practice with web servers. Apache has this > exact same structure.
Apache once had this structure, starting with 2.4 (Jessie) it changed to
/etc/apache2/conf-available
/etc/apache2/conf-enabled
and it doesn't have conf.d anymore.
Apache then loads everything from /etc/apache2/conf-enabled/*.conf.
Admins are exected to put their stuff in conf-available and then run
`a2enconf confname` which creates a symlink in conf-enabled to
conf-available (then, I hate doing that and I have my ansible role just
put my conf files in conf-enabled).
Note that for apache files in those directories are not expected to
define virtualhosts.
> I'm not against modifying the main nginx config file to support this, but I'm
> against the proposed solution and not sure I see an obvious solution that
> seems
> to be sensible.
I find apache's solution very sensible, actually.
On Tue, Jul 26, 2016 at 10:37:41PM -0700, Michael Lustfield wrote:
> Obviously, conf.d/*.conf has been around for a *LONG* time and isn't
> going anywhere.
Also apache's conf.d has been there for a very long time, but it simply
went away :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
