Regenerate the doc pages, and one of them was a live bug #68

2026-08-31T15:28:39Z

paulhitt commented

2026-08-31 15:28:39 +00:00

(Migrated from gitlab.com)

Part of #7. Follows paulhitt/flamenet-e2e!1.

Two pages regenerated. One is routine; the other was broken in production.

`/spec` — routine

Picks up §8.9b, the §22.4 reconciliation, and the corrected §15 table.

`/self-hosting` — a live bug

f80cc3c fixed the quick start a day ago. One of those fixes never reached the
public page, because the page is generated and nobody re-ran the generator.

Live until this merges:

$ curl -s https://flamenetmessenger.com/self-hosting | grep -c "docker network create web"
0

<p>Then:</p>
<pre class="bash"><code>docker compose up -d</code></pre>

A self-hoster following the published instructions still hits
network web declared as external, but could not be found — after waiting
for the image build. Exactly the failure the fix removed.

The direction that has no guard

Every generated page carries a banner saying edits made there are lost.
Nothing catches the reverse — a source edited and the page never regenerated.

That direction is worse. The banner failure is loud: your edit disappears and
you notice. This one is silent and stays served. It has now happened at least
twice — build-doc-pages.sh was itself broken for a month after the repository
split, and /spec, /audit and /security were served as current throughout.

#7 tracks the CI check that would catch it: run the generator, then
git diff --exit-code Resources/Views/.

Deploy

Pages ship inside the relay image, so neither correction is live until this goes
through the staging gate.

Part of #7. Follows paulhitt/flamenet-e2e!1. Two pages regenerated. One is routine; the other was broken in production. ### `/spec` — routine Picks up §8.9b, the §22.4 reconciliation, and the corrected §15 table. ### `/self-hosting` — a live bug `f80cc3c` fixed the quick start a day ago. One of those fixes never reached the public page, because the page is **generated** and nobody re-ran the generator. Live until this merges: ``` $ curl -s https://flamenetmessenger.com/self-hosting | grep -c "docker network create web" 0 ``` ```html <p>Then:</p> <pre class="bash"><code>docker compose up -d</code></pre> ``` A self-hoster following the published instructions still hits `network web declared as external, but could not be found` — **after** waiting for the image build. Exactly the failure the fix removed. ### The direction that has no guard Every generated page carries a banner saying edits made *there* are lost. Nothing catches the reverse — a source edited and the page never regenerated. That direction is worse. The banner failure is **loud**: your edit disappears and you notice. This one is **silent** and stays served. It has now happened at least twice — `build-doc-pages.sh` was itself broken for a month after the repository split, and `/spec`, `/audit` and `/security` were served as current throughout. #7 tracks the CI check that would catch it: run the generator, then `git diff --exit-code Resources/Views/`. ### Deploy Pages ship inside the relay image, so neither correction is live until this goes through the staging gate.

paulhitt commented

2026-08-31 16:01:58 +00:00

(Migrated from gitlab.com)

mentioned in commit 154dc21816

mentioned in commit 154dc21816a06268280788ac5bee431f3b4b13e2

paulhitt (Migrated from gitlab.com) merged commit 154dc21816 into main

2026-08-31 16:01:58 +00:00

paulhitt commented

2026-09-09 18:59:26 +00:00

(Migrated from gitlab.com)

changed the description

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#68

Regenerate the doc pages, and one of them was a live bug #68

/spec — routine

/self-hosting — a live bug

The direction that has no guard

Deploy

`/spec` — routine

`/self-hosting` — a live bug