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

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

README.md

@@ -36,7 +36,6 @@ We have several tutorials to get you started.
 - Tutorials to create a new server from scratch on a cloud provider & run TLJH
   on it. These are **recommended** if you do not have much experience setting up
   servers.
-
   - [Digital Ocean](https://the-littlest-jupyterhub.readthedocs.io/en/latest/install/digitalocean.html)
   - [OVH](https://the-littlest-jupyterhub.readthedocs.io/en/latest/install/ovh.html)
   - [Google Cloud](https://the-littlest-jupyterhub.readthedocs.io/en/latest/install/google.html)

docs/contributing/dev-setup.md

@@ -61,7 +61,6 @@ The easiest & safest way to develop & test TLJH is with [Docker](https://www.doc
 
 8. Make some changes to the repository. You can test easily depending on what
    you changed.
-
    - If you changed the `bootstrap/bootstrap.py` script or any of its dependencies,
      you can test it by running `python3 /srv/src/bootstrap/bootstrap.py`.
    - If you changed the `tljh/installer.py` code (or any of its dependencies),

docs/howto/auth/awscognito.md

@@ -24,7 +24,6 @@ application to your `tljh` configuration.
 1. Create a user pool [Getting Started with User Pool](https://docs.aws.amazon.com/cognito/latest/developerguide/getting-started-with-cognito-user-pools.html).
 
    When you have completed creating a user pool, app, and domain you should have the following settings available to you:
-
    - **App client id**: From the App client page
 
    - **App client secret** From the App client page

docs/howto/auth/github.md

@@ -26,7 +26,6 @@ You'll need a GitHub account in order to complete these steps.
 ## Step 1: Create a GitHub application
 
 1. Go to the [GitHub OAuth app creation page](https://github.com/settings/applications/new).
-
    - **Application name**: Choose a descriptive application name (e.g. `tljh`)
 
    - **Homepage URL**: Use the IP address or URL of your JupyterHub. e.g. `` http(s)://<my-tljh-url>` ``.

docs/howto/auth/google.md

@@ -51,7 +51,6 @@ and create a new project:
   ```
 
 - You will have to fill a form with:
-
   - **Application type**: Choose _Web application_
 
   - **Name**: A descriptive name for your OAuth client ID (e.g. `tljh-client`)

docs/howto/user-env/user-environment.md

@@ -180,7 +180,6 @@ To upgrade the Python version of the user environment, one can:
   environment, but you may do so manually.
 
   **Steps:**
-
   1.  Activate the user environment, if using ssh. If the terminal was
       started with JupyterHub, this step can be skipped:
 

docs/install/azure.md

@@ -51,7 +51,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     ```
 
 5.  **Choose an Ubuntu server for your VM**:
-
     - Click `Ubuntu Server 22.04 LTS.`
 
     - Make sure `Resource Manager` is selected in the next screen and click **Create**
@@ -61,7 +60,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     ```
 
 6.  Customise the Virtual Machine basics:
-
     - **Subscription**. Choose the "Free Trial" if this is what you're using. Otherwise, choose a different plan. This is the billing account that will be charged.
     - **Resource group**. Resource groups let you keep your Azure tools/resources together in an availability region (e.g. WestEurope). If you already have one you'd like to use it select that resource.
 
@@ -89,7 +87,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     - **Inbound port rules**. Leave the defaults for now, and we will update these later on in the Network configuration step.
 
 7.  Before clicking on "Next" we need to select the RAM size for the image.
-
     - For this we need to make sure we have enough RAM to accommodate your users. For example, if each user needs 2GB of RAM, and you have 10 total users, you need at least 20GB of RAM on the machine. It's also good to have a few GB of "buffer" RAM beyond what you think you'll need.
 
     - Click on **Change size** (see image below)
@@ -105,7 +102,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     - Select a suitable image (to check available images and prices in your region [click on this link](https://azuremarketplace.microsoft.com/en-gb/marketplace/apps/Canonical.UbuntuServer?tab=PlansAndPrice/?wt.mc_id=TLJH-github-taallard)).
 
 8.  Disks (Storage):
-
     - **Disk options**: select the OS disk type there are options for SDD and HDD. **SSD persistent disk** gives you a faster but more expensive disk than HDD.
 
     - **Data disk**. Click on create and attach a new disk. Select an appropriate type and size and click ok.
@@ -120,7 +116,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     ```
 
 9.  Networking
-
     - **Virtual network**. Leave the default values selected.
     - **Subnet**. Leave the default values selected.
     - **Public IP address**.Leave the default values selected. This will make your server accessible from a browser.
@@ -132,9 +127,7 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     ```
 
 10. Management
-
     - Monitoring
-
       - **Boot diagnostics**. Choose "On".
       - **OS guest diagnostics**. Choose "Off".
       - **Diagnostics storage account**. Leave as the default.
@@ -150,7 +143,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
     ```
 
 11. Advanced settings
-
     - **Extensions**. Make sure there are no extensions listed
     - **Cloud init**. We are going to use this section to install TLJH directly into our Virtual Machine.
 
@@ -177,7 +169,6 @@ We start by creating the Virtual Machine in which we can run TLJH (The Littlest
 12. Check the summary and confirm the creation of your Virtual Machine.
 
 13. Check that the creation of your Virtual Machine worked.
-
     - Wait for the virtual machine to be created. This might take about 5-10 minutes.
 
     - After completion, you should see a similar screen to the one below:

docs/install/jetstream.md

@@ -17,15 +17,15 @@ users and a user environment with packages you want installed running on
 
 We'll create a new Jetstream 2 virtual machine and have it automatically install The Littlest JupyterHub (TLJH) at first boot.
 
-1. Log in to the [Jetstream 2 portal](https://use.jetstream-cloud.org/). You must have (and select) an allocation in order to launch instances. Click the allocation you want to charge.
-2. Click **Create** ➜ **Instance**.
-3. From the list of images, select **Ubuntu 24.04** (Jammy or newer is required for current TLJH releases).
-4. In the **Create Instance** dialog:
+1.  Log in to the [Jetstream 2 portal](https://use.jetstream-cloud.org/). You must have (and select) an allocation in order to launch instances. Click the allocation you want to charge.
+2.  Click **Create** ➜ **Instance**.
+3.  From the list of images, select **Ubuntu 24.04** (Jammy or newer is required for current TLJH releases).
+4.  In the **Create Instance** dialog:
     1. Set a descriptive **Instance Name** (this is used in the default hostname and helps users recognize it).
     2. Choose an **Instance Size**. We suggest `m3.small` (2 vCPUs / 8 GiB RAM) or larger for more than a couple of users. The absolute minimum TLJH can start with is about **1 GiB** RAM, but you'll quickly run out with real workloads.
-        - See the resource estimation guide: [Choosing resources](/howto/admin/resource-estimation) for help picking CPU, RAM, and disk.
+       - See the resource estimation guide: [Choosing resources](/howto/admin/resource-estimation) for help picking CPU, RAM, and disk.
     3. (Optional) Increase the **Volume Size** if you expect many users or large datasets. You can not easily shrink later.
-5. Expand **Advanced Options**, then locate the **Boot Script** field. Replace any placeholder content with the following script (the whole content should just be this):
+5.  Expand **Advanced Options**, then locate the **Boot Script** field. Replace any placeholder content with the following script (the whole content should just be this):
 
     ```bash
     #!/bin/bash
@@ -40,21 +40,23 @@ We'll create a new Jetstream 2 virtual machine and have it automatically install
     Notes:
     - The script runs only once, during the initial boot.
     - Keep it minimal—adding extra commands often slows install or causes failures if something prompts for input.
-6. Launch the instance (click **Create Instance** / **Launch**).
-7. You'll return to the instances dashboard. Your new instance will transition through provisioning states. It generally takes about 5 minutes for the TLJH install to finish after the VM first reports as active.
-8. Once the status shows **Ready** (or the VM indicates it is running), copy the displayed **Hostname**. It looks like:
+
+6.  Launch the instance (click **Create Instance** / **Launch**).
+7.  You'll return to the instances dashboard. Your new instance will transition through provisioning states. It generally takes about 5 minutes for the TLJH install to finish after the VM first reports as active.
+8.  Once the status shows **Ready** (or the VM indicates it is running), copy the displayed **Hostname**. It looks like:
 
          yourinstancename.xxx0000000.projects.jetstream-cloud.org
 
     Here `xxx0000000` is your allocation ID.
-9. Open that hostname in a web browser (http on port 80). You should see the JupyterHub login page. Your browser will warn about the site not being secure (no HTTPS)—we'll enable HTTPS in the next step.
+
+9.  Open that hostname in a web browser (http on port 80). You should see the JupyterHub login page. Your browser will warn about the site not being secure (no HTTPS)—we'll enable HTTPS in the next step.
 10. Log in with the `<admin-user-name>` you used in the boot script. Since this is the first login, you'll be prompted to set a password. Choose a strong password and store it safely. This password is now the credential for that admin user.
 11. (Optional) Verify the install by SSHing to the instance as `exouser` (Jetstream's default user):
-     ```bash
-     ssh [email protected]
-     sudo tljh-config show | grep version || echo "Version not yet recorded (install still running?)"
-     ```
-     If the install is still finishing you may briefly get a 503 proxy error or the version line may not appear yet—wait another minute and try again.
+    ```bash
+    ssh [email protected]
+    sudo tljh-config show | grep version || echo "Version not yet recorded (install still running?)"
+    ```
+    If the install is still finishing you may briefly get a 503 proxy error or the version line may not appear yet—wait another minute and try again.
 12. You now have a working JupyterHub. Continue below to secure it with HTTPS.
 
 ## Step 2: Enable HTTPS
@@ -64,34 +66,35 @@ Encrypted (HTTPS) access is strongly recommended before inviting users.
 See the full guide: [Enable HTTPS](/howto/admin/https). Below is a quick recipe for using the default Jetstream-provided hostname.
 
 1. SSH to the instance as `exouser`:
-    ```bash
-    ssh [email protected]
-    ```
+   ```bash
+   ssh [email protected]
+   ```
 2. Configure Let's Encrypt (replace with a real email you control):
-    ```bash
-    sudo tljh-config set https.enabled true
-    sudo tljh-config set https.letsencrypt.email [email protected]
-    sudo tljh-config add-item https.letsencrypt.domains yourinstancename.xxx0000000.projects.jetstream-cloud.org
-    sudo tljh-config reload proxy
-    ```
+   ```bash
+   sudo tljh-config set https.enabled true
+   sudo tljh-config set https.letsencrypt.email [email protected]
+   sudo tljh-config add-item https.letsencrypt.domains yourinstancename.xxx0000000.projects.jetstream-cloud.org
+   sudo tljh-config reload proxy
+   ```
 3. Wait ~30–60 seconds, then reload the site using https://. If certificate issuance fails, check the logs:
-    ```bash
-    sudo journalctl -u traefik --since "10 minutes ago" | grep -i acme
-    ```
+   ```bash
+   sudo journalctl -u traefik --since "10 minutes ago" | grep -i acme
+   ```
 
 Tips:
-* Make sure ports 80 and 443 are open in your Jetstream security group (they are open by default for new projects; adjust only if you customized network policies).
-* If you later attach a custom domain, add it with another `add-item` command and reload the proxy again.
+
+- Make sure ports 80 and 443 are open in your Jetstream security group (they are open by default for new projects; adjust only if you customized network policies).
+- If you later attach a custom domain, add it with another `add-item` command and reload the proxy again.
 
 ## Step 3: Customize your JupyterHub deployment
 
 Next common tasks:
 
-* Add additional users or admins: [User management](/howto/admin/add-users)
-* Install Python / conda packages for all users: [Customize user environment](/howto/user-env)
-* Install optional system packages: `sudo apt install <package>` (restart user servers afterwards)
-* Pre-install JupyterLab extensions: see [Enable extensions](/howto/admin/enable-extensions)
-* Update TLJH itself: [Upgrading TLJH](/topic/installer-upgrade-actions)
+- Add additional users or admins: [User management](/howto/admin/add-users)
+- Install Python / conda packages for all users: [Customize user environment](/howto/user-env)
+- Install optional system packages: `sudo apt install <package>` (restart user servers afterwards)
+- Pre-install JupyterLab extensions: see [Enable extensions](/howto/admin/enable-extensions)
+- Update TLJH itself: [Upgrading TLJH](/topic/installer-upgrade-actions)
 
 Browse the full How-To index for more: [/howto/index](/howto/index)
 
@@ -110,5 +113,5 @@ When asking for help about TLJH, it is often useful to provide:
 - Your TLJH version (`sudo tljh-config show | grep version` if present in config) and the output of `lsb_release -a` for the OS
 - Any custom installer flags or `tljh-config` changes you have applied
 
-This information helps others debug and answer more quickly    sudo journalctl -u traefik --since "10 minutes ago" | grep -i acme
-.
+This information helps others debug and answer more quickly sudo journalctl -u traefik --since "10 minutes ago" | grep -i acme
+.

docs/topic/whentouse.md

@@ -22,11 +22,9 @@ container technology in administering user sessions.
 The choice between TLJH and Z2JH ultimately comes down to only a few questions:
 
 1. Do you want your hub and all users to live on a **single, larger machine** vs. spreading users on a **cluster of smaller machines** that are scaled up or down?
-
    - If you can use a single machine, we recommend **The Littlest JupyterHub**.
    - If you wish to use multiple machines, we recommend **Zero to JupyterHub for Kubernetes**.
 
 2. Do you **need to use container technology**?
-
    - If no, we recommend **The Littlest JupyterHub**.
    - If yes, we recommend **Zero to JupyterHub for Kubernetes**.

docs/troubleshooting/logs.md

@@ -81,7 +81,6 @@ easier. Here are some very basic tips on effective `journalctl` usage.
    [less](<https://en.wikipedia.org/wiki/Less_(Unix)>). This allows you to
    scroll up / down, search for specific words, etc. Some common keyboard shortcuts
    are:
-
    - Arrow keys to move up / down / left / right
    - `G` to navigate to the end of the logs
    - `g` to navigate to the start of the logs