I've noticed that the installer script for RHEL and CentOS modifies the default nginx.conf:
|
if [ -e /etc/nginx/nginx.conf ]; then |
|
/usr/bin/rm /etc/nginx/nginx.conf |
|
fi |
|
cat << EOF >> /etc/nginx/nginx.conf |
Modifying the default config file could cause problems with multi-application deployments or existing proxy servers.
Instead, this script should act similar to Ubuntu with a small tweak. In Ubuntu, nginx modular configurations are loaded from /etc/nginx/conf.d/*.conf and /etc/nginx/sites-enabled/*.conf; the latter is loaded to provide a similar interface to Apache2 in Debian and Ubuntu. In RHEL, only /etc/nginx/conf.d/*.conf is loaded by default. This comes from the default config file's line include /etc/nginx/conf.d/*.conf;.
Therefore, JAWA should place its modular configuration inside the /etc/nginx/conf.d/ directory.
I've noticed that the installer script for RHEL and CentOS modifies the default nginx.conf:
JAWA/bin/rhel_installer.sh
Lines 331 to 334 in fbfdaf1
Modifying the default config file could cause problems with multi-application deployments or existing proxy servers.
Instead, this script should act similar to Ubuntu with a small tweak. In Ubuntu, nginx modular configurations are loaded from
/etc/nginx/conf.d/*.confand/etc/nginx/sites-enabled/*.conf; the latter is loaded to provide a similar interface to Apache2 in Debian and Ubuntu. In RHEL, only/etc/nginx/conf.d/*.confis loaded by default. This comes from the default config file's lineinclude /etc/nginx/conf.d/*.conf;.Therefore, JAWA should place its modular configuration inside the
/etc/nginx/conf.d/directory.