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
In the jupyter-docker-stacks Docs, the proposed solution for HTTPS connection to the notebook is to mount the certificates via volume (this we can already do via custom mounts config 🎉) and passing extra config parameters to the start-notebook.sh commands.
Motivation
In the jupyter-docker-stacks Docs, the proposed solution for HTTPS connection to the notebook is to mount the certificates via volume (this we can already do via
custom mounts
config 🎉) and passing extra config parameters to thestart-notebook.sh
commands.There are other Jupyter config options that might be useful in this way, e.g. setting up a password
https://jupyter-docker-stacks.readthedocs.io/en/latest/using/common.html#jupyter-server-options
Proposal
Add a new configuration option, perhaps titles
JUPYTER_SERVER_OPTIONS
, by default empty, and pass it on when starting a container.If this all sound okay to you @csadorf I can take this on.
The text was updated successfully, but these errors were encountered: