pixie-lab 0.4.3__tar.gz → 0.4.4__tar.gz

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/CHANGELOG.md

@@ -11,6 +11,17 @@ operator-facing summary.
 
 ## [Unreleased]
 
+## [0.4.4] - 2026-07-27
+
+### Added
+
+**One-click live-env setup.** The Live env page now has a **Set up live
+env** button that fetches the `pixie-live-env` image + its arch-headless
+netboot bundle and selects the image in a single action, with a live
+progress bar -- no more hopping to the Catalog tab, fetching two entries
+by hand, and copying a `content_sha256` onto the Live env page. The
+manual "select by content sha" form remains as an advanced override.
+
 ## [0.4.3] - 2026-07-26
 
 ### Removed

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pixie-lab
-Version: 0.4.3
+Version: 0.4.4
 Summary: Bare-metal netboot appliance: catalog + fetch + NBD + PXE + TFTP + operator TUI in one container
 Project-URL: Homepage, https://github.com/safl/pixie
 Project-URL: Repository, https://github.com/safl/pixie
@@ -67,13 +67,18 @@ top nav has Machines, Catalog, Events, and Settings.
 2. Click Fetch on a row to download it. The status pill ticks
    through downloading -> decompressing -> unpacking with a
    `bytes / total` counter so you see progress live.
-3. Power-cycle a target with pixie in its DHCP next-server chain.
+3. For the live-env boot modes (`pixie-inventory` / `pixie-tui` /
+   `pixie-flash-*`), Fetch the `pixie-live-env` image + its netboot
+   bundle, then set the image's `content_sha256` on the Live env page
+   (`/ui/live-env`) or via `PIXIE_LIVE_ENV_IMAGE_SHA`. Those modes
+   nbdboot that image; until it's selected they render `unavailable`.
+4. Power-cycle a target with pixie in its DHCP next-server chain.
    A first contact shows up on `/ui/machines` with the default
    `ipxe-exit` boot mode. Open the row to bind a mode + image.
-4. `pixie-inventory` prompts the live env to POST an inventory
+5. `pixie-inventory` prompts the live env to POST an inventory
    blob; the target's disks + NICs + memory show up on the
    machine detail page.
-5. Flash modes (`pixie-flash-once`, `pixie-flash-always`) require
+6. Flash modes (`pixie-flash-once`, `pixie-flash-always`) require
    a target disk serial that came in on the inventory. The
    binding form disables Save until that prerequisite is met.
 
@@ -85,9 +90,11 @@ event log, settings, NBD-export records, and persistent-overlay
 records. `blobs/<sha>/blob` holds fetched disk images.
 `artifacts/<sha>/{vmlinuz,initrd,manifest.json}` holds unpacked
 netboot bundles. `overlays/<mac>/<image_sha>/<profile>.qcow2` holds
-per-machine writable overlays for the `nbdboot` boot mode.
-`live-env/` holds the pixie live env kernel + initrd + squashfs the
-netboot-pc bake produced.
+per-machine writable overlays for the `nbdboot` boot mode. The live env
+(`pixie-inventory` / `pixie-tui` / `pixie-flash-*`) is the fetched
+`pixie-live-env` disk image, selected by `PIXIE_LIVE_ENV_IMAGE_SHA` /
+the Live env page and nbdbooted like any other image, so it lives in
+`blobs/` + `artifacts/` too - there is no separate live-env directory.
 
 Both admin password and display timezone / strftime pattern have
 env-var overrides plus DB overrides via `/ui/settings`; env wins

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/README.md

@@ -39,13 +39,18 @@ top nav has Machines, Catalog, Events, and Settings.
 2. Click Fetch on a row to download it. The status pill ticks
    through downloading -> decompressing -> unpacking with a
    `bytes / total` counter so you see progress live.
-3. Power-cycle a target with pixie in its DHCP next-server chain.
+3. For the live-env boot modes (`pixie-inventory` / `pixie-tui` /
+   `pixie-flash-*`), Fetch the `pixie-live-env` image + its netboot
+   bundle, then set the image's `content_sha256` on the Live env page
+   (`/ui/live-env`) or via `PIXIE_LIVE_ENV_IMAGE_SHA`. Those modes
+   nbdboot that image; until it's selected they render `unavailable`.
+4. Power-cycle a target with pixie in its DHCP next-server chain.
    A first contact shows up on `/ui/machines` with the default
    `ipxe-exit` boot mode. Open the row to bind a mode + image.
-4. `pixie-inventory` prompts the live env to POST an inventory
+5. `pixie-inventory` prompts the live env to POST an inventory
    blob; the target's disks + NICs + memory show up on the
    machine detail page.
-5. Flash modes (`pixie-flash-once`, `pixie-flash-always`) require
+6. Flash modes (`pixie-flash-once`, `pixie-flash-always`) require
    a target disk serial that came in on the inventory. The
    binding form disables Save until that prerequisite is met.
 
@@ -57,9 +62,11 @@ event log, settings, NBD-export records, and persistent-overlay
 records. `blobs/<sha>/blob` holds fetched disk images.
 `artifacts/<sha>/{vmlinuz,initrd,manifest.json}` holds unpacked
 netboot bundles. `overlays/<mac>/<image_sha>/<profile>.qcow2` holds
-per-machine writable overlays for the `nbdboot` boot mode.
-`live-env/` holds the pixie live env kernel + initrd + squashfs the
-netboot-pc bake produced.
+per-machine writable overlays for the `nbdboot` boot mode. The live env
+(`pixie-inventory` / `pixie-tui` / `pixie-flash-*`) is the fetched
+`pixie-live-env` disk image, selected by `PIXIE_LIVE_ENV_IMAGE_SHA` /
+the Live env page and nbdbooted like any other image, so it lives in
+`blobs/` + `artifacts/` too - there is no separate live-env directory.
 
 Both admin password and display timezone / strftime pattern have
 env-var overrides plus DB overrides via `/ui/settings`; env wins

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/docs/src/deployment.md

@@ -13,8 +13,7 @@ The recommended layout on the deploy host:
     compose.yml
     envvars
     envvars.example
-    data/                  <- persistent state (state.db, blobs, artifacts)
-        live-env/          <- staged pixie live env (vmlinuz + initrd + squashfs)
+    data/                  <- persistent state (state.db, blobs, artifacts, overlays)
 ```
 
 `compose.yml` is generated by `pixie-lab init` and shouldn't need
@@ -69,7 +68,7 @@ unattended). Flags choose how far the wipe goes:
 
 - `--data` - also delete `data/`: `state.db` (catalog, machines,
   events, exports, overlays, settings), every fetched blob and unpacked
-  artifact, all overlay volumes, and the staged `live-env/`.
+  artifact, and all overlay volumes.
   `data/` is a bind mount (`./data:/var/lib/pixie`), not a named
   volume, so purge unlinks it directly - `podman compose down -v`
   alone would not touch it.
@@ -93,19 +92,31 @@ podman build -t pixie:local -f Containerfile .
 cd /opt/pixie && podman compose --env-file envvars up -d
 ```
 
-### Stage the live env
-
-The `pixie-flash-*`, `pixie-inventory`, and `pixie-tui` boot modes chain
-into pixie's live env (`vmlinuz` + `initrd` + `live.squashfs`). Open the
-**Live env** page in the UI (`/ui/live-env`) and click **Fetch live
-env**: pixie pulls the netboot-pc bake from `PIXIE_LIVE_ENV_SRC`
-(default: the latest pixie GitHub release's
-`pixie-live-env-x86_64.tar.gz`) and stages it under `PIXIE_LIVE_ENV_DIR`
-itself - no manual bake or copy. For an air-gapped install, point
-`PIXIE_LIVE_ENV_SRC` (or the live override on the Live env page) at a
-local mirror of that tarball. You can still build it yourself with
-`make build VARIANT=netboot-pc` and drop the three files into
-`data/live-env/` by hand.
+### Select the live env
+
+The `pixie-flash-*`, `pixie-inventory`, and `pixie-tui` boot modes boot
+pixie's live env: the **`pixie-live-env`** disk image (the nosi
+`arch-headless` base with the pixie CLI + `pixie-on-tty1` service
+injected) booted over ephemeral nbdboot, exactly like the `nbdboot`
+mode. Two UI steps set it up:
+
+1. On the **Catalog** page (`/ui/catalog`), Fetch the `pixie-live-env`
+   image and its `nosi arch-headless netboot bundle`. Both ship in the
+   bundled seed catalog (`PIXIE_SEED_CATALOG`, default on); if your
+   catalog is empty, import the release `catalog.toml` first. The image
+   is an `img.gz` release asset (its `src` is the latest pixie release's
+   `pixie-live-env-x86_64.img.gz`, ~900 MiB); the bundle carries the
+   matching kernel + initrd.
+2. On the **Live env** page (`/ui/live-env`), paste the fetched image's
+   `content_sha256` (shown on its catalog row, or in the release's
+   `pixie-live-env-x86_64.content-sha256` asset) into **Image content
+   sha** and Save. Equivalently, set `PIXIE_LIVE_ENV_IMAGE_SHA` in
+   `envvars`.
+
+Until an image is selected **and** its bundle + blob are fetched, the
+`pixie-*` boot modes render the readable `unavailable` plan rather than
+booting nothing. For an air-gapped install, mirror the `img.gz` + the
+oras bundle and point the two catalog entries' `src` at your mirror.
 
 ## Environment variables
 
@@ -144,20 +155,15 @@ behaviour. See [](boot-modes.md).
 
 **`PIXIE_DATA_DIR`** (default: `/var/lib/pixie`) - state root. Holds
 `state.db`, `blobs/` (fetched image bytes), `artifacts/` (extracted
-netboot bundles), `overlays/<alias>.qcow2`
+netboot bundles), and `overlays/<alias>.qcow2`
 (globally-named single-writer overlay volumes for nbdboot; see
-[](boot-modes.md)),
-`live-env/` (staged pixie live env).
-
-**`PIXIE_LIVE_ENV_DIR`** (default: `$PIXIE_DATA_DIR/live-env`) - the
-`pixie-*` boot modes degrade to an unavailable plan when this dir is
-missing or incomplete.
-
-**`PIXIE_LIVE_ENV_SRC`** (default: the latest pixie GitHub release's
-`pixie-live-env-x86_64.tar.gz`) - the tarball the dashboard **Fetch
-live-env** action downloads and stages into `PIXIE_LIVE_ENV_DIR`.
-Accepts `https://` or `oras://`; it must unpack to `vmlinuz` + `initrd`
-+ `live.squashfs`. Overridable live on the Live env page.
+[](boot-modes.md)).
+
+**`PIXIE_LIVE_ENV_IMAGE_SHA`** (default: unset) - the `content_sha256`
+of the fetched `pixie-live-env` disk image the `pixie-inventory` /
+`pixie-tui` / `pixie-flash-*` boot modes nbdboot. When unset, those
+modes render the `unavailable` plan. Overridable live on the Live env
+page (see [Select the live env](#select-the-live-env)).
 
 **`PIXIE_SEED_CATALOG`** (default: `1`) - seed a fresh (empty) catalog
 from the bundled curated catalog (the netboot-capable nosi subset) on

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/docs/src/hardware-quirks.md

@@ -5,7 +5,7 @@ pixie's live env end-to-end, and the kernel cmdline tokens that
 unblock them. Set the tokens via the Settings page
 (`/ui/settings`, "Live-env" card, "Extra kernel cmdline") or via
 `PIXIE_LIVE_ENV_EXTRA_CMDLINE` in `envvars`. Either path is
-appended verbatim to the `pixie-live-env.j2` kernel line, after
+appended verbatim to the live-env kernel line, after
 `pixie.mac=` + `bty.mac=` so last-token-wins on any conflict.
 
 The Settings page persists across restarts (state.db). The
@@ -21,14 +21,14 @@ Symptom pattern from the pixie access log:
 
     GET /pxe-bootstrap.ipxe                    200
     GET /pxe/<mac>                             200
-    GET /boot/pixie-live-env/vmlinuz           200
-    GET /boot/pixie-live-env/initrd            200
-    # ...silence. No /boot/pixie-live-env/live.squashfs fetch.
+    GET /artifacts/<sha>/vmlinuz               200
+    GET /artifacts/<sha>/initrd                200
+    # ...silence. No NBD connect to the live-env export.
 
 iPXE handed the kernel + initrd off to Linux, then Linux couldn't
 bring up the boot NIC (driver -EIO, DMA fail, ROM-BAR conflict,
-etc). live-boot has no interface to run `fetch=` through and the
-target hangs silently before any userspace runs.
+etc), so the initrd never connects the live-env image over NBD and
+the target hangs silently before any userspace runs.
 
 Get to a serial console (BMC SoL, USB-serial adapter, or physical
 COM1). If the console shows the kernel initialising, then falling
@@ -67,7 +67,7 @@ workaround kicks in the kernel logs:
     igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection
     igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex
 
-...and the live-boot initrd fetches the squashfs normally.
+...and the initrd connects the live-env image over NBD normally.
 
 ## Target firmware prerequisites (not cmdline)
 

pixie_lab-0.4.4/docs/src/quickstart.md

@@ -0,0 +1,85 @@
+# Quickstart
+
+Bring pixie up, point DHCP at it, and boot a first target.
+
+## Bring pixie up
+
+One command. It generates the config, starts the container, and waits
+until pixie answers healthy:
+
+```
+uv tool run pixie-lab deploy /opt/pixie --host-addr <LAN-IP>
+```
+
+`uv tool run` fetches `pixie-lab` into a throwaway environment (nothing
+to install or leave behind). `deploy` writes `compose.yml` + `envvars`
+into `/opt/pixie`, brings the stack up under `network_mode: host` (so
+TFTP + the NBD range + HTTP all reach the LAN), waits on `/healthz`, and
+prints the admin password it generated. The only default you usually
+set is `--host-addr` (otherwise auto-detected); override the rest with
+`--admin-password` / `--image` as needed.
+
+Host prerequisite: podman + a compose provider. Then log in at
+`http://<LAN-IP>:8080/`.
+
+> Prefer to review the generated files first? `uv tool run pixie-lab
+> init /opt/pixie` writes the same `compose.yml` + `envvars` without
+> starting anything; edit `envvars` (`PIXIE_HOST_ADDR` +
+> `PIXIE_ADMIN_PASSWORD`), then `cd /opt/pixie && podman compose
+> --env-file envvars up -d`.
+
+## Usage
+
+pixie is up; the rest is day-to-day operation. Point DHCP at it once,
+then drive everything from the web UI at `http://<LAN-IP>:8080/`.
+
+### Point DHCP at pixie
+
+Set your DHCP server to chain PXE targets through pixie's TFTP and
+iPXE bootstrap. See [](deployment.md#dhcp-handoff) for BIOS + UEFI
+dnsmasq recipes.
+
+### Add a catalog entry
+
+Open `http://<PIXIE_HOST_ADDR>:8080/ui/catalog` in a browser, log in
+with your admin password, and add a catalog entry with a source URL.
+Hit Fetch. Pixie pulls the bytes to disk (and for `img.gz` / `img.zst`
+inputs, decompresses on the way in). The row flips to `fetched` when
+the pipeline lands.
+
+### Select the live env
+
+The `pixie-inventory`, `pixie-tui`, and `pixie-flash-*` boot modes boot
+the `pixie-live-env` disk image (the operator TUI + CLI baked in) over
+nbdboot. On `/ui/catalog`, Fetch the **`pixie-live-env`** image and its
+**`nosi arch-headless netboot bundle`** (both ship in the seed catalog).
+Then open the **Live env** page (`/ui/live-env`) and set **Image content
+sha** to the fetched image's `content_sha256` (shown on its catalog
+row), or set `PIXIE_LIVE_ENV_IMAGE_SHA` in `envvars`. Until an image is
+selected, those boot modes render an `unavailable` plan. See
+[](deployment.md#select-the-live-env) for detail and the air-gapped
+path.
+
+### Bind a machine
+
+Once a target has PXEd at least once, it appears on `/ui/machines`.
+Click its MAC to open the machine detail page. Pick a boot mode from
+the card grid, pick an image, and Save. On the target's next PXE,
+pixie serves the plan you bound.
+
+See [](boot-modes.md) for what each mode does and how bindings pin a
+machine to an image and, for `nbdboot`, an overlay volume.
+
+## Tear it down
+
+One command, the inverse of deploy:
+
+```
+uv tool run pixie-lab purge /opt/pixie --all --yes
+```
+
+`--all` removes the container, its image, and `data/`. Drop `--all` to
+stop + remove the container only, or pick with `--data` / `--images`.
+Without `--yes` it prints the plan and asks first -- the `--data` /
+`--all` deletions are irreversible, and even a plain stop drops every
+live NBD export (any target booted `nbdboot` off pixie loses its root).

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pixie-lab"
-version = "0.4.3"
+version = "0.4.4"
 description = "Bare-metal netboot appliance: catalog + fetch + NBD + PXE + TFTP + operator TUI in one container"
 readme = "README.md"
 requires-python = ">=3.11"

{pixie_lab-0.4.3 → pixie_lab-0.4.4}/src/pixie/events/_kinds.py

@@ -196,7 +196,14 @@ EVENTS_CLEARED = "events.cleared"
 right after the wipe so the freshly-empty log still records who reset
 it and when; carries the deleted-row count in ``details``."""
 
-# ---------- live-env fetch ------------------------------------------
+# ---------- live env ------------------------------------------------
+
+LIVE_ENV_IMAGE_SELECTED = "live_env.image.selected"
+"""The one-click "Set up live env" action fetched the pixie-live-env
+image + its bundle and selected the image (set ``live_env.image_sha``).
+Carries the selected ``image_sha`` in ``details``."""
+
+
 # The canonical closed set. Every kind above is registered here; the
 # ``EventsLog.emit`` call rejects anything not in this frozenset.
 KNOWN_EVENT_KINDS: frozenset[str] = frozenset(
@@ -230,6 +237,7 @@ KNOWN_EVENT_KINDS: frozenset[str] = frozenset(
         AUTH_LOGIN_SUCCEEDED,
         AUTH_LOGIN_FAILED,
         EVENTS_CLEARED,
+        LIVE_ENV_IMAGE_SELECTED,
     }
 )
 

pixie_lab-0.4.4/src/pixie/web/_templates/live_env.html

@@ -0,0 +1,197 @@
+{% extends "layout.html" %}
+{% from "_partials/page_description.html" import page_description %}
+{% block title %}Live env - pixie{% endblock %}
+
+{% block subnav %}
+<nav class="navbar subnav-strip" aria-label="Section sub-navigation">
+    <div class="container">
+        <span class="subnav-jumps d-flex align-items-center flex-wrap">
+            <a href="#setup">Setup</a>
+            <a href="#advanced">Advanced</a>
+            <a href="#options">Options</a>
+        </span>
+    </div>
+</nav>
+{% endblock %}
+
+{% block content %}
+{% set ss = live_env_setup_state or {} %}
+{{ page_description('boombox', 'The pixie live env that the pixie-inventory / pixie-tui / pixie-flash-once / pixie-flash-always boot modes boot into: a disk image (the pixie-live-env catalog entry) booted over ephemeral nbdboot. Click Set up live env to fetch it and select it in one step; until then those boot modes render an "unavailable" plan.') }}
+
+{% if flash_error %}
+<div class="alert alert-danger py-2">{{ flash_error }}</div>
+{% endif %}
+
+{# ---- One-click setup -------------------------------------------- #}
+<div class="card shadow-sm mb-4" id="setup">
+    <div class="card-header bg-light d-flex align-items-center gap-2">
+        <h2 class="h5 mb-0"><i class="bi bi-boombox me-2"></i>Live env</h2>
+        {% if live_env_ready %}
+        <span class="badge text-bg-success ms-auto"><i class="bi bi-check-circle me-1"></i>ready</span>
+        {% elif ss.state == 'running' %}
+        <span class="badge text-bg-info ms-auto"><span class="spinner-border spinner-border-sm me-1" role="status"></span>setting up</span>
+        {% else %}
+        <span class="badge text-bg-warning ms-auto"><i class="bi bi-exclamation-triangle me-1"></i>not set up</span>
+        {% endif %}
+    </div>
+    <div class="card-body">
+        {% if live_env_ready %}
+        <p class="small mb-3">
+            Image <code>{{ live_env_image_sha.effective[:12] }}</code> is fetched and
+            selected; the <code>pixie-inventory</code> / <code>pixie-tui</code> /
+            <code>pixie-flash-*</code> modes nbdboot it. Nothing else to do.
+        </p>
+        {% else %}
+        <p class="small mb-3">
+            One click fetches the <code>pixie-live-env</code> image (~900&nbsp;MiB) +
+            its arch-headless netboot bundle from the catalog, then selects the image.
+            No catalog hopping or sha copying. It runs on the server; you can leave
+            this page. Re-running when everything is already fetched just re-selects.
+        </p>
+        {% endif %}
+
+        {# Progress (polled live while a setup runs). #}
+        <div id="setup-progress" class="{% if ss.state != 'running' %}d-none{% endif %} mb-3">
+            <div class="d-flex align-items-center gap-2 small mb-1">
+                <span class="spinner-border spinner-border-sm" role="status"></span>
+                <span id="setup-step">Fetching {{ ss.step or 'live env' }}{% if ss.phase %} ({{ ss.phase }}){% endif %}...</span>
+            </div>
+            <div class="progress" role="progressbar" style="height: 1.1rem;">
+                <div id="setup-bar" class="progress-bar progress-bar-striped progress-bar-animated"
+                     style="width: {% if ss.total_bytes %}{{ (100 * ss.bytes_downloaded / ss.total_bytes) | round(0, 'floor') }}{% else %}100{% endif %}%"></div>
+            </div>
+        </div>
+        <div id="setup-error" class="alert alert-danger py-2 small {% if ss.state != 'error' %}d-none{% endif %}">
+            <i class="bi bi-exclamation-triangle me-1"></i><span id="setup-error-msg">{{ ss.error }}</span>
+        </div>
+
+        <form method="post" action="/ui/live-env/setup" class="m-0">
+            <button type="submit" class="btn {% if live_env_ready %}btn-outline-secondary{% else %}btn-primary{% endif %}"
+                    id="setup-btn" {% if ss.state == 'running' %}disabled{% endif %}>
+                {% if ss.state == 'running' %}
+                <span class="spinner-border spinner-border-sm me-1" role="status"></span>Setting up...
+                {% else %}
+                <i class="bi bi-boombox me-1"></i>{% if live_env_ready %}Re-run setup{% else %}Set up live env{% endif %}
+                {% endif %}
+            </button>
+            <span class="text-muted small ms-2">Fetch + select in one step.</span>
+        </form>
+    </div>
+</div>
+
+{# ---- Advanced: select by content sha ---------------------------- #}
+<div class="card shadow-sm mb-4" id="advanced">
+    <div class="card-header bg-light fw-semibold">
+        <i class="bi bi-sliders me-1"></i>Advanced: select by content sha
+    </div>
+    <div class="card-body">
+        <p class="small text-muted mb-3">
+            Manual override of what Set up above does automatically: point the live env
+            at a specific fetched image by its <code>content_sha256</code> (from its
+            <a href="/ui/catalog">Catalog</a> row). The image plus its netboot bundle
+            (via the entry's <code>netboot_src</code>) must both be fetched.
+        </p>
+        <form method="post" action="/ui/live-env/image/edit" class="row g-3">
+            <div class="col-12">
+                <label for="live_env_image_sha" class="form-label">
+                    Image content sha
+                    <span class="badge text-bg-{% if live_env_image_sha.override %}primary{% else %}secondary{% endif %} ms-1">
+                        {% if live_env_image_sha.override %}override{% elif live_env_image_sha.effective %}env{% else %}unset{% endif %}
+                    </span>
+                </label>
+                <input type="text" id="live_env_image_sha" name="live_env_image_sha"
+                       class="form-control font-monospace"
+                       value="{{ live_env_image_sha.override }}"
+                       placeholder="(unset - live-env modes render the unavailable plan)"
+                       pattern="[0-9a-fA-F]{64}">
+                <div class="form-text">
+                    Blank falls back to <code>{{ live_env_image_sha.env }}</code> then unset.
+                    Effective:
+                    {% if live_env_image_sha.effective %}<code>{{ live_env_image_sha.effective }}</code>{% else %}<em class="text-muted">(none)</em>{% endif %}.
+                    {% if live_env_image_sha.updated_at %}<br>Last updated: <code>{{ live_env_image_sha.updated_at | fmt_ts }}</code>.{% endif %}
+                </div>
+            </div>
+            <div class="col-12">
+                <button type="submit" class="btn btn-outline-secondary"><i class="bi bi-check2 me-1"></i>Save</button>
+                <span class="text-muted small ms-2">
+                    Takes effect on the NEXT <code>GET /pxe/&lt;mac&gt;</code>; a target already mid-boot must be power-cycled.
+                </span>
+            </div>
+        </form>
+    </div>
+</div>
+
+{# ---- Options (config) ------------------------------------------- #}
+<div class="card shadow-sm mb-4" id="options">
+    <div class="card-header bg-light fw-semibold">
+        <i class="bi bi-gear me-1"></i>Options
+    </div>
+    <div class="card-body">
+        <form method="post" action="/ui/live-env/cmdline/edit" class="row g-3">
+            <div class="col-12">
+                <label for="extra_cmdline" class="form-label">
+                    Extra kernel cmdline
+                    <span class="badge text-bg-{% if live_env_extra_cmdline.override %}primary{% else %}secondary{% endif %} ms-1">
+                        {% if live_env_extra_cmdline.override %}override{% elif live_env_extra_cmdline.effective %}env{% else %}default{% endif %}
+                    </span>
+                </label>
+                <input type="text" id="extra_cmdline" name="extra_cmdline"
+                       class="form-control font-monospace"
+                       value="{{ live_env_extra_cmdline.override }}"
+                       placeholder="e.g. pci=realloc=on,nocrs"
+                       list="live-env-cmdline-suggestions">
+                <datalist id="live-env-cmdline-suggestions">
+                    <option value="pci=realloc=on,nocrs">
+                </datalist>
+                <div class="form-text">
+                    Tokens appended verbatim to the live-env kernel cmdline
+                    (after <code>pixie.mac=</code> / <code>bty.mac=</code>, so last-token-wins on any
+                    conflict). Whitespace-separated; single line. Blank falls back to
+                    <code>{{ live_env_extra_cmdline.env }}</code> then no append. A machine with its own
+                    <code>extra_cmdline</code> binding overrides this global. Effective:
+                    {% if live_env_extra_cmdline.effective %}<code>{{ live_env_extra_cmdline.effective }}</code>{% else %}<em class="text-muted">(none)</em>{% endif %}.
+                    Known-good values per hardware in
+                    <a href="https://github.com/safl/pixie/blob/main/docs/src/hardware-quirks.md" target="_blank" rel="noreferrer">docs/hardware-quirks.md</a>.
+                    {% if live_env_extra_cmdline.updated_at %}<br>Last updated: <code>{{ live_env_extra_cmdline.updated_at | fmt_ts }}</code>.{% endif %}
+                </div>
+            </div>
+            <div class="col-12">
+                <button type="submit" class="btn btn-primary"><i class="bi bi-check2 me-1"></i>Save</button>
+                <span class="text-muted small ms-2">
+                    Takes effect on the NEXT <code>GET /pxe/&lt;mac&gt;</code>; a target already mid-boot must be power-cycled.
+                </span>
+            </div>
+        </form>
+    </div>
+</div>
+
+{# Poll setup progress while a run is in flight; reload when it lands
+   so the ready badge + selected sha update. #}
+<script>
+(function () {
+    if ("{{ ss.state }}" !== "running") return;
+    var box = document.getElementById("setup-progress");
+    var step = document.getElementById("setup-step");
+    var bar = document.getElementById("setup-bar");
+    function poll() {
+        fetch("/ui/live-env/setup-state.json", { headers: { "Accept": "application/json" } })
+            .then(function (r) { return r.json(); })
+            .then(function (s) {
+                if (!s || s.state === "running") {
+                    if (step) step.textContent = "Fetching " + (s.step || "live env") +
+                        (s.phase ? " (" + s.phase + ")" : "") + "...";
+                    if (bar && s.total_bytes) {
+                        bar.style.width = Math.floor(100 * s.bytes_downloaded / s.total_bytes) + "%";
+                    }
+                    setTimeout(poll, 1500);
+                } else {
+                    // done or error -> reload to render the final state.
+                    location.reload();
+                }
+            })
+            .catch(function () { setTimeout(poll, 3000); });
+    }
+    setTimeout(poll, 1500);
+})();
+</script>
+{% endblock %}