First of all - thanks a lot for all your work, Guillaume!
Trying new 1.10.1 version of dotdeb-nginx I've noticed what I'd call inconsistency. After fresh installation
the directory /etc/nginx/modules-available is entirely empty, while /etc/nginx/modules-enabled contanis reference to all the modules in the form of:
I understand the need to get all the modules in the modules-enabled to be able to start nginx after upgrade from the versions prior to 1.10.
Still, this setup is quite different to the way how sites-available -> sites-enabled works or how apache2mods-available -> mods-enabled does. Also, direct links to /usr/share/nginx/modules-available/ seems violating the whole idea.
I'd suggest in this case make /etc/nginx/modules-available a symlink to /usr/share/nginx/modules-available/ and then make symlinks from modules-available to modules-enabled in a conventional way. Possibly, ngx-conf can be extended for this.
First of all - thanks a lot for all your work, Guillaume!
Trying new 1.10.1 version of dotdeb-nginx I've noticed what I'd call inconsistency. After fresh installation the directory
/etc/nginx/modules-available
is entirely empty, while/etc/nginx/modules-enabled
contanis reference to all the modules in the form of:I understand the need to get all the modules in the
modules-enabled
to be able to startnginx
after upgrade from the versions prior to 1.10.Still, this setup is quite different to the way how
sites-available
->sites-enabled
works or howapache2
mods-available
->mods-enabled
does. Also, direct links to/usr/share/nginx/modules-available/
seems violating the whole idea.I'd suggest in this case make
/etc/nginx/modules-available
a symlink to/usr/share/nginx/modules-available/
and then make symlinks frommodules-available
tomodules-enabled
in a conventional way. Possibly,ngx-conf
can be extended for this.