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

[pre-commit.ci] auto fixes from pre-commit.com hooks

Browse Source 
for more information, see https://pre-commit.ci
This commit is contained in:
pre-commit-ci[bot]
2022-10-26 17:17:19 +00:00
parent 12de64828c
commit 6a4078f977
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/source/reference/proxy.md
View File

@@ -7,9 +7,10 @@ Hub manages by default as a subprocess (it can be run externally, as well, and
typically is in production deployments). typically is in production deployments).
The upside to CHP, and why we use it by default, is that it's easy to install The upside to CHP, and why we use it by default, is that it's easy to install
and run (if you have nodejs, you are set!). The downsides are that and run (if you have nodejs, you are set!). The downsides are that
- it's a single process and
- does not support any persistence of the routing table. - it's a single process and
- does not support any persistence of the routing table.
So if the proxy process dies, your whole JupyterHub instance is inaccessible So if the proxy process dies, your whole JupyterHub instance is inaccessible
until the Hub notices, restarts the proxy, and restores the routing table. For until the Hub notices, restarts the proxy, and restores the routing table. For