Closed jakst closed 6 years ago
NGINX_CONFIG
sets the overarching config path. It is a parent concept. NGINX_DEV_INSTALL
is a child concept. For example, NGINX_CONFIG
can be set for html
or php
which contains underlying configs. In both cases you may want to run them in a local development mode. There may have been a change at some point that was not reflected in the docs or was committed in error. Let me take a look and get back to you..
I think what was missing was this:
if [[ $NGINX_DEV_INSTALL = "true" ]] && [[ $NGINX_CONFIG != "basic" ]]; then dev else echo "OK: Not installing development SSL certs or files"; fi
Since we do not want to install dev assets if someone is running in bare metal mode. Thoughts?
I just pushed an update to fix dangling dev. Thanks for pointing it out.
The new messages about bare metal make way more sense. Nice 👍
First
Dev mode is commented on this line, so it is never activated.
Second
Dev mode does not respect the env variable
NGINX_DEV_INSTALL
. In fact, there is not a single reference toNGINX_DEV_INSTALL
in the whole repository. Instead, some of the logic seems to reference theNGINX_CONFIG
variable instead.Example from docker-entrypoint.sh
Why does it check
NGINX_CONFIG
instead ofNGINX_DEV_INSTALL
?