commit d0370b7552020c11088b9e38200d50d2b4cc67c0
parent 1410ca0b04021d4692b684a2e944724d80eb9ba5
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Mon, 28 Sep 2026 04:03:11 -0400
docs: E2E_SHARDS; the homepage's Docker page says Build all uses containers whenever it can
CONTRIBUTING and SETUP: `E2E_SHARDS=N pnpm e2e:sharded`. umtool's projects
doc names E2E_UMTOOL_EXTRA_KINDS. The public homepage's "Building several
sites at once" page and its /docs blurb no longer call the container
pipeline opt-in behind a toggle: Build all sites builds in containers
whenever an engine is available, and the mode is a label (as PUBLISH.md
says).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Diffstat:
5 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -83,7 +83,7 @@ The npm script rebuilds the image first (layer cache covers unchanged deps, so
repeat builds are seconds), then runs `scripts/run-sharded-e2e.mjs`.
Shard count defaults to `min(max(2, cpus/2), 8)`. Override with
-`SHARDS=N pnpm e2e:sharded` or `node scripts/run-sharded-e2e.mjs --shards N`.
+`E2E_SHARDS=N pnpm e2e:sharded` or `node scripts/run-sharded-e2e.mjs --shards N`.
**Retries default to 0**, so a sharded run reports the same failures a sequential one
does. (The containers set `CI=true` because `playwright.config`'s
diff --git a/SETUP.md b/SETUP.md
@@ -298,7 +298,7 @@ pnpm e2e # sequential run on the host (next dev, port 3
For a faster parallel run, `pnpm e2e:sharded` splits the suite across N Docker
containers (needs **Docker**; the container image ships the browser, so no
`playwright install` there). Shard count defaults to `min(max(2, cpus/2), 8)`;
-override with `SHARDS=N pnpm e2e:sharded`.
+override with `E2E_SHARDS=N pnpm e2e:sharded`.
To run multiple checkouts / dev servers / e2e suites at once without port
collisions, see [WORKTREES.md](WORKTREES.md).
diff --git a/homepage/content/docs.ts b/homepage/content/docs.ts
@@ -67,7 +67,7 @@ export const DOCS: DocEntry[] = [
file: "deploy-docker.md",
title: "Building several sites at once",
blurb:
- "The opt-in Docker pipeline: parallel per-site builds in isolated containers.",
+ "Build all sites: parallel per-site builds in isolated containers, whenever a container engine is available.",
group: "publish",
},
{
diff --git a/homepage/content/docs/deploy-docker.md b/homepage/content/docs/deploy-docker.md
@@ -1,11 +1,13 @@
# Building several sites at once
-If one corpus publishes several sites, the default build handles them one after
-another. The container pipeline builds them **in parallel**, in isolated
-containers, and then deploys them serially. It is opt-in, and the ordinary build
-is unchanged and remains the default.
-
-Turn it on in the editor's settings, or from the toggle on the deploy page.
+If one corpus publishes several sites, **Build all sites** builds them **in
+parallel**, in isolated containers, and then deploys them serially, whenever a
+container engine is available on the machine. With none, it builds them one after
+another instead. A single site's own build always runs one at a time.
+
+The editor's settings and its Sites page also show a build mode, Basic or Docker.
+Today that choice is only a label: Build all sites uses containers whenever it
+can, whichever mode is set.
## What you need
diff --git a/umtool/docs/projects.md b/umtool/docs/projects.md
@@ -79,7 +79,7 @@ fail when somebody special-cases a kind in a page — which no page test can see
`components/projects/`** — a grep for lines carrying both a kind id and the
word `kind`;
- **`RESERVED_BROWSE` equals the real static pages**;
-- **a kind injected through `UMTOOL_EXTRA_KINDS` reaches the index, the chips and
+- **a kind injected through `E2E_UMTOOL_EXTRA_KINDS` reaches the index, the chips and
the CLI with no code edit at all**.
## Where the code is
