Hi,
On Fri, Jun 24, 2016 at 11:28:54 -0700, Michael Lustfield wrote:
> We already include conf.d/*.conf which can be used exactly as you
> described.
Not really. It includes files on the level of "new sites",
that is new virtual hosts.
My suggestion includes snippets on the level of the default
virtual host, inside that.
> In my personal deployments, I remove sites-enabled/default and
> only use conf.d/*.conf files.
I find it strange, that an admin is expected to remove a
file on nearly all use cases. Why do you ship it, if 99% of
the admins are expected to remove it anyway?
Removing a file isn't something that other (Debian)
packages are allowed to, I'd guess.
Let's look at the javascript-common package. It has exactly
one goal: Make sure, that the default virtual host serves
libjs-* files under /javascript. Under the current design
of nginx-common, it can't do that. It would need to remove
sites-enabled/default and replace it or something.
Now the next package enters, say icinga-cgi, which wants to
have /icinga on the default host. What shell it do on
nginx? Again kill sites-enabled/default?
> Is there any reason this doesn't meet your needs?
It does only meet my needs on the "admin wants to do
everything on his/her own" level. And on that level, I can
also kill /etc/nginx/nginx.conf and replace it by my wanted
config. No need to have this whole conf.d stuff at all.
But on the level of "Admin wants to augment the default
virtual host", it doesn't work well.
And it fails to work, if we want to do that augmenting
using packages.
To summarise: Please point me to docs on how to make say
javascript-common work on nginx.
Cheers
Elrond
p.s.: Please next time include me in the reply, as
submitters don't get nnnnnn@bugs mails.
