mirror of
https://github.com/jupyterhub/the-littlest-jupyterhub.git
synced 2025-12-18 21:54:05 +08:00
fix absolute refs
myst seems to create different refs than sphinx
This commit is contained in:
@@ -17,7 +17,7 @@ so attackers can not easily gain control of the system.
|
||||
:::{important}
|
||||
You should make sure an admin user is present when you **install** TLJH
|
||||
the very first time. It is recommended that you also set a password
|
||||
for the admin at this step. The {ref}`--admin <topic/customizing-installer/admin>`
|
||||
for the admin at this step. The [`--admin`] (/topic/customizing-installer/admin)
|
||||
flag passed to the installer does this. If you had forgotten to do so, the
|
||||
easiest way to fix this is to run the installer again.
|
||||
:::
|
||||
|
||||
@@ -8,9 +8,9 @@ HTTPS encrypts traffic so that usernames, passwords and your data are
|
||||
communicated securely. sensitive bits of information are communicated
|
||||
securely. The Littlest JupyterHub supports automatically configuring HTTPS
|
||||
via [Let's Encrypt](https://letsencrypt.org), or setting it up
|
||||
{ref}`manually <howto/admin/https/manual>` with your own TLS key and
|
||||
[manually](#howto-admin-https-manual) with your own TLS key and
|
||||
certificate. Unless you have a strong reason to use the manual method,
|
||||
you should use the {ref}`Let's Encrypt <howto/admin/https/letsencrypt>`
|
||||
you should use the [Let's Encrypt](#howto-admin-https-letsencrypt)
|
||||
method.
|
||||
|
||||
:::{note}
|
||||
@@ -35,7 +35,7 @@ similar to this:
|
||||
If the machine you are running on is not reachable from the internet -
|
||||
for example, if it is a machine internal to your organization that
|
||||
is cut off from the internet - you can not use this method. Please
|
||||
set up a DNS entry and HTTPS {ref}`manually <howto/admin/https/manual>`.
|
||||
set up a DNS entry and HTTPS [manually](#howto-admin-https-manual).
|
||||
:::
|
||||
|
||||
To enable HTTPS via letsencrypt:
|
||||
@@ -115,4 +115,4 @@ and now access your Hub securely at <https://yourhub.yourdomain.edu>.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
If you're having trouble with HTTPS, looking at the {ref}`traefik proxy logs <troubleshooting/logs/traefik>` might help.
|
||||
If you're having trouble with HTTPS, looking at the [traefik proxy logs](troubleshooting-logs-traefik) might help.
|
||||
|
||||
@@ -11,7 +11,7 @@ the cloud provider of your choice.
|
||||
|
||||
Currently there are instructions to resize your resources on the following providers:
|
||||
|
||||
- {ref}`Digital Ocean <howto/providers/digitalocean/resize>`.
|
||||
- [Digital Ocean](howto-providers-digitalocean-resize)
|
||||
|
||||
Once resources have been reallocated, you must tell TLJH to make use of these resources,
|
||||
and verify that the resources have become available.
|
||||
@@ -20,7 +20,7 @@ and verify that the resources have become available.
|
||||
|
||||
1. Once you have resized your server, tell the JupyterHub to make use of
|
||||
these new resources. To accomplish this, follow the instructions in
|
||||
{ref}`topic/tljh-config` to set new memory or CPU limits and reload the hub. This can be completed
|
||||
[](/topic/tljh-config) to set new memory or CPU limits and reload the hub. This can be completed
|
||||
using the terminal in the JupyterHub (or via SSH-ing into your VM and using this terminal).
|
||||
|
||||
2. TLJH configuration options can be verified by viewing the tljh-config output.
|
||||
|
||||
@@ -36,7 +36,7 @@ over time. We generally recommend between 40-60% of your total class size to sta
|
||||
|
||||
Depending on what kind of work your users are doing, they will use different amounts
|
||||
of memory. The easiest way to determine this is to run through a typical user
|
||||
workflow yourself, and measure how much memory is used. You can use {ref}`howto/admin/nbresuse`
|
||||
workflow yourself, and measure how much memory is used. You can use [](/howto/admin/nbresuse)
|
||||
to determine how much memory your user is using.
|
||||
|
||||
A good rule of thumb is to take the maximum amount of memory you used during
|
||||
|
||||
Reference in New Issue
Block a user