commit 2aabde260d97cf647034366f8b71a10777738e2f
parent fc5ccd226bdbdb00845daa9c286a17ee4f6d06c4
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Mon, 28 Sep 2026 09:35:18 -0400
docs: no build mode — PUBLISH, RUNNING_IN_DOCKER and the homepage's Docker page (O6c)
PUBLISH.md's "Building every site in containers" says there is no mode to
set; RUNNING_IN_DOCKER's fallback section names Build all instead of
`buildPipeline.mode = "docker"`; the homepage's "Building several sites at
once" drops the label paragraph (nothing to switch on).
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Diffstat:
3 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/PUBLISH.md b/PUBLISH.md
@@ -360,9 +360,8 @@ any limit.
deploys them serially — a large speedup when you host several sites, and stronger
isolation than building one site at a time in `export/`. It does so **whenever a
container engine answers** (`docker version`), and builds serially on the host when
-none does. The **Build pipeline → mode** (Basic / Docker, in Settings or on the
-/sites toggle) is persisted and shown, but no build reads it today: it is a label,
-not a switch. A single site's build always runs in `export/`, one at a time.
+none does. There is no mode to set. A single site's build always runs in `export/`,
+one at a time.
**Prerequisites.**
diff --git a/RUNNING_IN_DOCKER.md b/RUNNING_IN_DOCKER.md
@@ -541,8 +541,8 @@ silently loses formats), `ffmpeg`/`ffprobe`, `whisper-cli` (statically linked),
### The multi-site build pipeline falls back inside a container
-The editor can fan per-site export builds out across containers
-(`buildPipeline.mode = "docker"`, see [PUBLISH.md](PUBLISH.md#building-every-site-in-containers)). Inside a container there
+The editor's **Build all sites** fans per-site export builds out across containers
+whenever a container engine answers (see [PUBLISH.md](PUBLISH.md#building-every-site-in-containers)). Inside a container there
is no `docker` binary, so that path is unavailable. It already handles this — the
build logs
diff --git a/homepage/content/docs/deploy-docker.md b/homepage/content/docs/deploy-docker.md
@@ -3,11 +3,8 @@
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.
+another instead. A single site's own build always runs one at a time. There is
+nothing to switch on.
## What you need
