You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.The text was updated successfully, but these errors were encountered: