The live self-hosting page still has the broken instructions #7

New Issue

2026-08-31T15:28:13Z

paulhitt commented

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

(Migrated from gitlab.com)

f80cc3c fixed the self-hosting quick start, which was broken in three ways.
One of those fixes never reached the public page, because the page is
generated and nobody re-ran the generator.

Live right now:

$ 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>

So 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. That is the exact failure the fix removed a day ago.

Running Scripts/build-doc-pages.sh regenerates it, and the diff is the missing
step. Being fixed in the same MR as the spec regeneration.

🔴 The process gap is the real issue

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 vanishes), this one is
silent and stays live.

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 the whole time.

Done when

The self-hosting page regenerated and deployed
CI fails when a generated page differs from what the generator would
produce — run it and git diff --exit-code Resources/Views/

⚠️ That job needs pandoc and the flamenet-e2e checkout, which is why it is not
already there. FLAMENET_E2E_DIR exists for exactly this.

`f80cc3c` fixed the self-hosting quick start, which was broken in three ways. One of those fixes never reached the public page, because the page is **generated** and nobody re-ran the generator. Live right now: ``` $ 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> ``` So 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. That is the exact failure the fix removed a day ago. Running `Scripts/build-doc-pages.sh` regenerates it, and the diff is the missing step. Being fixed in the same MR as the spec regeneration. ### 🔴 The process gap is the real issue 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 vanishes), this one is silent and stays live. 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 the whole time. ### Done when - [ ] The self-hosting page regenerated and deployed - [ ] CI fails when a generated page differs from what the generator would produce — run it and `git diff --exit-code Resources/Views/` ⚠️ That job needs pandoc and the `flamenet-e2e` checkout, which is why it is not already there. `FLAMENET_E2E_DIR` exists for exactly this.

paulhitt commented

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

(Migrated from gitlab.com)

mentioned in commit 74052cef9f

mentioned in commit 74052cef9f5ce56ad141b112c8b7d6a742339217

paulhitt commented

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

(Migrated from gitlab.com)

mentioned in merge request !5