Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0912

The image serves the site the canonical pipeline produced

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
4
Waiting on
I0909
Holds back
I0930
Behind it in all
7
Evidence
0 of 3
In the waySubjectDetail
issueI0909I0909 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0912

majordomus plan verify I0912

majordomus plan done I0912

What it is

Objective
Build the served documentation and site assets in the container with the same pipeline local development and the Pages deployment already use, and carry exactly those outputs into the runtime stage.
Why
A second site build inside a Dockerfile is a second source of truth for the documentation, and the two will disagree the day one of them is fixed. The pipeline already exists and already has a check.
Now
One pipeline builds the site and scripts/site-deploy publishes it to Pages. Nothing builds it for a container.
Wanted
The container build calls the canonical generation and site build, copies their outputs, and the runtime serves those assets through the existing server architecture with no duplicated content.
Done when
unknown: the record declares no `completion`
Risk
The derived site content is gitignored, so a clean checkout has to generate it before it can be built. A container build that skips generation produces an image with no documentation and no error.

Acceptance

  • The container build invokes the repository's canonical generation and site build, not a copy of their steps
  • The runtime stage carries exactly the produced assets and no source of the site
  • The served assets are byte-identical to what the canonical pipeline produces locally
  • The contribution of the assets to the image size is measured and reported
Validation
bash test/run.shmajordomus generate --check
Evidence required
single_site_pipelineassets_in_imageasset_size
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
deploy/flyscripts
Not
A second site generator, a second Zola invocation path or a shell reimplementation of the buildChanging how Pages is deployed
Depends on
I0909
Priority
p0
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.