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

what-is-jupyterhub: clarifications (single-user and kernels)

Browse Source 
- Single-user servers are same you get with `jupyter notebook`.
- Kernels by default in single-user server environment but don't have
  to be.
This commit is contained in:
Richard Darst
2019-09-10 14:36:25 +03:00
committed by YuviPanda
parent b6e4225482
commit fd2919b36f
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/source/explanation/concepts.md
View File

@@ -238,8 +238,12 @@ included in the JupyterHub logs.
## Single-user notebook server ## Single-user notebook server
The role of the spawner is to start the **single-user notebook The **single-user notebook server** is the same thing you get by
server** - basically, running the command `jupyter notebook`. running `jupyter notebook` or `jupyter lab` from the command line -
the actual Jupyter user interface for a single person.
The role of the spawner is to start this server - basically, running
the command `jupyter notebook`.
Actually it doesn't run that, it runs `jupyterhub-singleuser` which Actually it doesn't run that, it runs `jupyterhub-singleuser` which
first communicates with the hub to say "I'm alive" before running a first communicates with the hub to say "I'm alive" before running a
completely normal Jupyter server. The single-user server can be completely normal Jupyter server. The single-user server can be
@@ -302,6 +306,7 @@ Does anything need to be said here?
- how extensions work in lab compared to notebook - how extensions work in lab compared to notebook
## Kernel ## Kernel
Normally, our tour of the Jupyter ecosystem would stop here. But, Normally, our tour of the Jupyter ecosystem would stop here. But,
@@ -334,7 +339,9 @@ a different environment.
What does this mean? There is yet *another* layer of configurability. What does this mean? There is yet *another* layer of configurability.
Each kernel can run a different programming language, with different Each kernel can run a different programming language, with different
software, and so on. The most common way they are configured is by software, and so on. By default, they would run in the same
environment as the single-user notebook server, and the most common
other way they are configured is by
running in different Python virtual environments or conda running in different Python virtual environments or conda
environments. They can be started and killed independently (there is environments. They can be started and killed independently (there is
normally one per notebook you have open). The kernels is what uses normally one per notebook you have open). The kernels is what uses