fmt: run prettier

Author: zonca

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
+.