hazza/jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/jupyterhub.git synced 2025-10-07 18:14:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Corrected some spelling errors.
This commit is contained in:
Lili Yao
2022-10-26 15:44:52 +11:00
committed by GitHub
parent 41cbcc9502
commit 76f7ff4721
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
examples/bootstrap-script/README.md
View File

@@ -9,7 +9,7 @@ _Providing writeable storage for LDAP users_
Your Jupyterhub is configured to use the LDAPAuthenticator and DockerSpawer. Your Jupyterhub is configured to use the LDAPAuthenticator and DockerSpawer.
- The user has no file directory on the host since your are using LDAP. - The user has no file directory on the host since you are using LDAP.
- When a user has no directory and DockerSpawner wants to mount a volume, - When a user has no directory and DockerSpawner wants to mount a volume,
the spawner will use docker to create a directory. the spawner will use docker to create a directory.
Since the docker daemon is running as root, the generated directory for the volume Since the docker daemon is running as root, the generated directory for the volume
@@ -23,7 +23,7 @@ Another use would be to copy initial content, such as tutorial files or referenc
material, into the user's space when a notebook server is newly spawned. material, into the user's space when a notebook server is newly spawned.
You can define your own bootstrap process by implementing a `pre_spawn_hook` on any spawner. You can define your own bootstrap process by implementing a `pre_spawn_hook` on any spawner.
The Spawner itself is passed as parameter to your hook and you can easily get the contextual information out of the spawning process. The Spawner itself is passed as a parameter to your hook and you can easily get the contextual information out of the spawning process.
Similarly, there may be cases where you would like to clean up after a spawner stops. Similarly, there may be cases where you would like to clean up after a spawner stops.
You may implement a `post_stop_hook` that is always executed after the spawner stops. You may implement a `post_stop_hook` that is always executed after the spawner stops.