This changes the dockerfile to be more flexibly configured at runtime.
These environment variables include
MONGO_HOST=hostname of mongo server (default=localhost)
MONGO_PORT=hostname of mongo port (default=27017)
MONGO_USERNAME=username for authentication of mongo host (default none, and no auth is configured)
MONGO_PASSWORD=password for authentication of mongo host (default none, need to configure if MONGO_USERNAME)
NDVIZHOST=host where ndviz can be found, used for dynamically generating links, will autoappend this query parameter to all initial management console URLs (default none, behavior off by default)
NDVIZPORT = port where ndviz can be found
this is all done through an entrypoint script which is a modification of the default jetty entrypoint script.
It also adds a default root_context to redirect web users to the management console.. when deploying this as a docker it is safe to assume that this is the only service running on this port, or else the dockerfile has been modified and people are free to reconfigure it as such.
i have also reconfigured permissions to run this container as jetty user by default and disable root permissions making it safer to run.
This changes the dockerfile to be more flexibly configured at runtime.
These environment variables include
MONGO_HOST=hostname of mongo server (default=localhost) MONGO_PORT=hostname of mongo port (default=27017) MONGO_USERNAME=username for authentication of mongo host (default none, and no auth is configured) MONGO_PASSWORD=password for authentication of mongo host (default none, need to configure if MONGO_USERNAME) NDVIZHOST=host where ndviz can be found, used for dynamically generating links, will autoappend this query parameter to all initial management console URLs (default none, behavior off by default) NDVIZPORT = port where ndviz can be found
this is all done through an entrypoint script which is a modification of the default jetty entrypoint script.
It also adds a default root_context to redirect web users to the management console.. when deploying this as a docker it is safe to assume that this is the only service running on this port, or else the dockerfile has been modified and people are free to reconfigure it as such.
i have also reconfigured permissions to run this container as jetty user by default and disable root permissions making it safer to run.