Remove configurable-http-proxy references from docs

This commit is contained in:
Srinivas Nyayapati
2020-02-19 09:33:17 -05:00
parent 044f159078
commit f253f04f25
2 changed files with 4 additions and 7 deletions

View File

@@ -18,10 +18,8 @@ Hub environment
=============== ===============
JupyterHub is run from a python3 virtual environment located in ``/opt/tljh/hub``. It 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`` uses the system's installed python and is owned by root. It also contains a binary install
install of `configurable-http-proxy <https://github.com/jupyterhub/configurable-http-proxy>`_ of `traefik <http://traefik.io/>`_. This virtual environment is completely managed by TLJH.
and a binary install of `traefik <http://traefik.io/>`_. This virtual environment is
completely managed by TLJH.
User environment User environment
================ ================
@@ -60,10 +58,9 @@ hard to access the ``tljh-config`` command used to change most config parameters
Systemd Units 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. #. ``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 #. ``traefik.service`` - starts traefik proxy that manages HTTPS
In addition, each running Jupyter user gets their own systemd unit of the name ``jupyter-<username>``. In addition, each running Jupyter user gets their own systemd unit of the name ``jupyter-<username>``.

View File

@@ -8,7 +8,7 @@ Looking at Logs
They contain a forensic record of what individual pieces of software were doing 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. 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 <https://www.freedesktop.org/software/systemd/man/journalctl.html>`_. user's notebook server. All the logs are accessible via `journalctl <https://www.freedesktop.org/software/systemd/man/journalctl.html>`_.
The installer also writes logs to disk, to help with cases where the The installer also writes logs to disk, to help with cases where the
installer did not succeed. installer did not succeed.