Warn in the Baseline that a non-default origin needs a rebuild - #31
Merged
Conversation
Clean-machine smoke (2026-09-02, publication-gate item): a fresh public clone builds and serves a working instance first try — migrations apply, both containers go healthy, and POST /api/rooms returns 201 — but only at the origin baked at build time. Published on any other port, the canonical-origin redirect 308s every request, API included, to the dead default, and the Baseline section gave no hint why. The Configuration section already explains the build argument; this links the trap to the steps that spring it. Ordered-By: Hugo0 Order: https://github.com/peanutprotocol/peanutsplit/blob/main/ops/steward/HANDOFF-2026-09-02-showhn.md
Hugo0
added a commit
that referenced
this pull request
Sep 2, 2026
Readers arriving from a link saw licensing prose first and a paragraph about an unused Fastify app; the product, the try-it link and the self-host command were below the fold. Put those on top, with the site's card as the hero image, and say who pays for it in one line. The contributing and stewardship wording kept the policy (maintainer-led, issue before feature PR) but read as hostile; soften the tone, not the rule. STEWARDSHIP still said the repo was not public; it has been since 1 September. SELF-HOSTING still listed the clean-machine smoke test as an open gate; it passed today (PR #31). Claude-Session: https://claude.ai/code/session_01NKWpwUpsVvQzSMcDrqvmrE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task 4 of the Show-HN handoff (report + doc-PR lane only).
Smoke result — the publication-gate item PASSES with one doc gap. Fresh anonymous clone of the now-public repo →
cp .env.example .env→docker compose up --build(host ports overridden 3000→24361 / 5433→24362 via a compose override because this box occupies both): image builds, migrations apply, db+app go healthy (~the app's own HEALTHCHECK reports healthy),/healthcheckanswers, and POST /api/rooms creates a room (201, full room+member+token) when the request host matches the built origin.The gap: the baked
NEXT_PUBLIC_BASE_URLdefault (http://localhost:3000) canonical-redirects every request — API included — arriving on any other host:port. A self-hoster who edits the compose ports (or fronts it with a hostname) gets an instance that 308s everything to a dead URL with no hint. The Configuration section documents the build arg; the Baseline section now points at the trap. One paragraph, docs-only.Teardown verified: containers, volumes, local images, clone dir all removed.