From f253f04f25af1d1d4b39c22a0146702b186c238e Mon Sep 17 00:00:00 2001 From: Srinivas Nyayapati Date: Wed, 19 Feb 2020 09:33:17 -0500 Subject: [PATCH] Remove configurable-http-proxy references from docs --- docs/topic/installer-actions.rst | 9 +++------ docs/troubleshooting/logs.rst | 2 +- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/topic/installer-actions.rst b/docs/topic/installer-actions.rst index 21e381d..748086b 100644 --- a/docs/topic/installer-actions.rst +++ b/docs/topic/installer-actions.rst @@ -18,10 +18,8 @@ Hub environment =============== JupyterHub is run from a python3 virtual environment located in ``/opt/tljh/hub``. It -uses the system's installed python and is owned by root. It also contains a ``npm`` -install of `configurable-http-proxy `_ -and a binary install of `traefik `_. This virtual environment is -completely managed by TLJH. +uses the system's installed python and is owned by root. It also contains a binary install +of `traefik `_. This virtual environment is completely managed by TLJH. User environment ================ @@ -60,10 +58,9 @@ hard to access the ``tljh-config`` command used to change most config parameters Systemd Units ============= -TLJH places 3 systemd units on your computer. They all start on system startup. +TLJH places 2 systemd units on your computer. They all start on system startup. #. ``jupyterhub.service`` - starts the JupyterHub service. -#. ``configurable-http-proxy.service`` - starts the nodejs based proxy that is used by JupyterHub. #. ``traefik.service`` - starts traefik proxy that manages HTTPS In addition, each running Jupyter user gets their own systemd unit of the name ``jupyter-``. diff --git a/docs/troubleshooting/logs.rst b/docs/troubleshooting/logs.rst index 017b68d..315289f 100644 --- a/docs/troubleshooting/logs.rst +++ b/docs/troubleshooting/logs.rst @@ -8,7 +8,7 @@ Looking at Logs They contain a forensic record of what individual pieces of software were doing before things went bad, and can help us understand the problem so we can fix it. -TLJH collects logs from JupyterHub, Configurable HTTP Proxy, & from each individual +TLJH collects logs from JupyterHub, Traefik Proxy, & from each individual user's notebook server. All the logs are accessible via `journalctl `_. The installer also writes logs to disk, to help with cases where the installer did not succeed.