I absolutely can't disagree that, if a (drupal, wordpress, etc.) web
app package maintainer wants their package to work out of the box,
nginx being preferred should not be a hold-up.
Obviously, conf.d/*.conf has been around for a *LONG* time and isn't
going anywhere.
It's possible some people may modify nginx to read conf.d/* or some
other custom prefix, so using conf.d/<anything> leaves me a little bit
nervous about using it here, but I also feel like this has
historically been 'the place' for those configurations.
The package maintainer will have to know they have absolutely zero
control on what happens outside of location ^~ /<their_app> { } ( side
note... let's try to force that fact ), but it's entirely possible to
make this work.
My proposed solution is:
nginx.conf reads conf.d/*.conf
default server reads conf.d/*.include_in_default
Whether this is a good idea or not, I'm not entirely certain. It's the
best solution I've been able to come up with.
