Hi,
On Tue, Jul 26, 2016 at 10:37:41 -0700, Michael Lustfield wrote:
> 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.
Right,
> Obviously, conf.d/*.conf has been around for a *LONG* time and isn't
> going anywhere.
right.
[...]
> 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.
They're usually aware that there are other paths, that
other packages/etc own. That's why we have the
javascript-common package for example. drupal, wordpress,
etc can depend on it to get the /javascript location
filled with content.
> My proposed solution is:
> nginx.conf reads conf.d/*.conf
> default server reads conf.d/*.include_in_default
That's exactly what I was proposing! :)
My only difference was: Instead of
"conf.d/*.include_in_default" I was proposing
"SOMEDIR/*.conf".
I would still recommend to use a new subdir for it.
Don't clutter up one dir with different types of stuff.
That might lead to confusion.
So maybe "default-server-includes.d/*.conf"?
> 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.
Same with me. And it will certainly get us a big step
forward. And I don't think it will be a bad commitment for
the future.
Can we remove the "wontfix" tag?
Your comments highly suggest to me, that this isn't a
wontfix anymore?
Elrond
