mm/jupyterhub-deploy-docker
1
0
Fork 0
Code Pull Requests Releases Activity

A few more wording edits

Browse Source
This commit is contained in:
Carol Willing 2016-04-18 08:42:32 -07:00
parent c8b2c94fcd
commit f1851d6dd3
1 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -246,16 +246,19 @@ DOCKER_CONTAINER_IMAGE=jupyterhub/pyspark-notebook:2d878db5cbff \
### If I change the name of the Notebook server image to spawn, do I need to restart JupyterHub?
Yes. JupyterHub reads its configuration and the container image name for
DockerSpawner. This sets the name of the Notebook server image to spawn
during startup. It you change the name of the Docker image to spawn, you will
need to restart the JupyterHub container.
Yes. JupyterHub reads its configuration which includes the container image
name for DockerSpawner. JupyterHub uses this configuration to determine the
Notebook server image to spawn during startup.
If you change DockerSpawner's name of the Docker image to spawn, you will
need to restart the JupyterHub container for changes to occur.
In this reference deployment, cookies are persisted to a Docker volume on the
host. Restarting JupyterHub might cause a blip in user service as the
JupyterHub container restarts, but users will not have to login again to their
notebook servers. However, users may need to refresh their browser to
re-establish connections to active Notebook kernels.
Hub's host. Restarting JupyterHub might cause a temporary blip in user
service as the JupyterHub container restarts. Users will not have to login
again to their individual notebook servers. However, users may need to
refresh their browser to re-establish connections to the running Notebook
kernels.
### How can I backup a user's notebook directory?