zhangyiss/the-littlest-jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/the-littlest-jupyterhub.git synced 2025-12-18 21:54:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #325 from znicholls/docs-reading

Browse Source 
Few updates from reading through the docs
This commit is contained in:
Erik Sundell
2021-10-22 14:04:47 +02:00
committed by GitHub
parent 26811a8e8c a02ed26978
commit 56b6521e29
2 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/install/custom-server.rst
View File

@@ -34,7 +34,7 @@ Pre-requisites
#. A server running Ubuntu 18.04 where you have root access.
#. At least **1GB** of RAM on your server.
#. Ability to ``ssh`` into the server & run commands from the prompt.
#. A **IP address** where the server can be reached from the browsers of your target audience.
#. An **IP address** where the server can be reached from the browsers of your target audience.
If you run into issues, look at the specific :ref:`troubleshooting guide <troubleshooting/providers/custom>`
for custom server installations.
@@ -67,7 +67,7 @@ Step 1: Installing The Littlest JupyterHub
:ref:`topic/customizing-installer` documents other options that can be passed to the installer.
#. Press ``Enter`` to start the installation process. This will take 5-10 minutes,
and will say 'Done!' when the installation process is complete.
and will say ``Done!`` when the installation process is complete.
#. Copy the **Public IP** of your server, and try accessing ``http://<public-ip>`` from
your browser. If everything went well, this should give you a JupyterHub login page.

3
docs/troubleshooting/providers/custom.rst
View File

@@ -7,6 +7,9 @@ Troubleshooting issues on your own server
This is an incomplete list of issues people have run into
when installing TLJH on their own servers, and ways they
have fixed them.
Before trying any of them, also consider whether turning your machine on and off
and/or deleting the VM and starting over could solve the problem;
it has done so on a surprisingly high number of occasions!
Outgoing HTTP proxy required
============================