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

Cleanup references

Browse Source
This commit is contained in:
YuviPanda
2024-06-10 18:31:36 -07:00
parent 3caea2a463
commit 7852dbc1dc
3 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -64,7 +64,7 @@ JupyterHub itself doesn't actually manage your users. It has a
database of users, but it is usually connected with some other system database of users, but it is usually connected with some other system
that manages the usernames and passwords. When someone tries to log that manages the usernames and passwords. When someone tries to log
in to JupyteHub, it asks the in to JupyteHub, it asks the
**authenticator**([basics](authenticators-users-basics), **authenticator**([basics](authenticators),
[reference](../reference/authenticators)) if the [reference](../reference/authenticators)) if the
username/password is valid(&). The authenticator returns a username(&), username/password is valid(&). The authenticator returns a username(&),
which is passed on to the spawner, which has to use it to start that which is passed on to the spawner, which has to use it to start that
@@ -113,7 +113,7 @@ services you are using.
### Spawner ### Spawner
The **spawner** ([basics](spawners-basics), The **spawner** ([basics](spawners),
[reference](../reference/spawners)) is the real core of [reference](../reference/spawners)) is the real core of
JupyterHub: when someone wants a notebook server, the spawner allocates JupyterHub: when someone wants a notebook server, the spawner allocates
resources and starts the server. The notebook server could run on the resources and starts the server. The notebook server could run on the
@@ -196,7 +196,7 @@ running, the notebooks). By default, the hub starts the proxy
automatically automatically
and stops the proxy when the hub stops (so that connections get and stops the proxy when the hub stops (so that connections get
interrupted). But when you [configure the proxy to run interrupted). But when you [configure the proxy to run
separately](../reference/separate-proxy), separately](separate-proxy),
user's connections will continue to work even without the hub. user's connections will continue to work even without the hub.
The default proxy is **ConfigurableHttpProxy** which is simple but The default proxy is **ConfigurableHttpProxy** which is simple but
@@ -229,7 +229,7 @@ do configure it, you'll know).
### Services ### Services
JupyterHub has the concept of **services** JupyterHub has the concept of **services**
([basics](services-basics), ([basics](services),
[reference](../reference/services)), which are other web services [reference](../reference/services)), which are other web services
started by the hub, but otherwise are not necessarily related to the started by the hub, but otherwise are not necessarily related to the
hub itself. They are often used to do things related to Jupyter hub itself. They are often used to do things related to Jupyter

2
docs/source/reference/services.md
View File

@@ -1,4 +1,4 @@
(services)= (services-reference)=
# Services # Services

1
docs/source/tutorial/getting-started/services-basics.md
View File

@@ -1,3 +1,4 @@
(services)=
# External services # External services
When working with JupyterHub, a **Service** is defined as a process When working with JupyterHub, a **Service** is defined as a process