feat(demo): list the demo's sign-ins on /beta and link into it per game
Some checks failed
PR checks / checks (pull_request) Failing after 2m16s
Some checks failed
PR checks / checks (pull_request) Failing after 2m16s
The public demo (demo.runicgateway.com) is live, so the site's demo slot can be switched on. Two decisions of record, PLAN.md §15: - D82: /beta reads the demo's GET /api/v1/public/settings demo.logins on the server, caches it for a minute, and lists the published sign-ins with the next wipe. If the demo does not answer, /beta links to its sign-in page instead. Gate two reads as in place. - D83: a deep link into a game module's pages carries data-demo-game, and applyBrand.mjs fills it only for games in the new mounted demoGames list. The Rust features gain links into /rust and /rust/servers/demo. UO's stay hidden on a Rust demo. The public-demo not-built entry is removed, because its resolvedBy was met. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
57
PLAN.md
57
PLAN.md
@@ -232,12 +232,12 @@ Taken by the org lead (Colby Whitlock) on 2026-08-19. Recorded so they are not r
|
||||
| **D9** | **No analytics.** No tracking scripts, no third-party requests, no cookie banner. | Reverse-proxy access logs are the only traffic data. |
|
||||
| **D10** | **Support routes to Discord and Gitea issues.** Invite: `https://discord.gg/t2Jav8yT4g`. | §10. Discord is the front door; Gitea takes issues from anyone with an account, which today is nobody outside the org — §14, N3. |
|
||||
| **D11** | **Keep the existing emblem.** `runic-emblem.png` is the mark on both the website and the Android launcher icon; the site adopts it rather than drawing a new one. | §11. Revision 1's "draw a new geometric mark" recommendation is withdrawn. |
|
||||
| **D12** | **A public demo instance is planned but out of scope today** — a Proxmox VM running the full stack including ServUO, with restricted settings and an hourly automatic reset. | §15. The IA reserves the slot so it lands later without a restructure. |
|
||||
| **D12** | **A public demo instance is planned but out of scope today** — a Proxmox VM running the full stack including ServUO, with restricted settings and an hourly automatic reset. | §15. The IA reserves the slot so it lands later without a restructure. **Built 2026-10-27** as `demo.runicgateway.com`, on Rust with a two-hour reset; the site reaches it through D82 and D83 (§15). |
|
||||
| **D13** | **Publish the existing address.** No mailbox has been created at the domain and the org lead elected not to wait for one: `whitlocktech@gmail.com` is the published contact wherever the site needs one — `/privacy`, `/terms`, `/community`, the Play listing — and `docs/SECURITY.md` keeps the address it already carries. | Taken 2026-08-19, superseding §14 N2 as a blocker. The address lives **only** in `brand.json` (§7), never in prose, so moving to `privacy@`/`security@` later is a file edit and a restart. Phase 0's PR 0.10 is withdrawn, not deferred. |
|
||||
|
||||
**Decisions after D13 are recorded where they were taken**, in the section describing the phase that
|
||||
raised them, rather than appended here — a decision is only re-litigated when its reasoning is
|
||||
somewhere other than the thing it decided. The count of record is **seventy-nine**:
|
||||
somewhere other than the thing it decided. The count of record is **eighty-three**:
|
||||
|
||||
| # | Where | What it settled |
|
||||
|---|---|---|
|
||||
@@ -261,6 +261,8 @@ somewhere other than the thing it decided. The count of record is **seventy-nine
|
||||
| D70–D71 | §16, "How phase 15 built it" | The Rust group is fifteen pages, one per admin screen where it can be; the Rust event kinds are checked against the module's own classification |
|
||||
| D72–D74 | §16, "How phase 16 built it" | The RunicNPC subgroup is eight pages with a shared profile-field reference; the API check compares signatures and every data shape's field names; the site's API page carries the current API only, with no decision numbers and no version history |
|
||||
| D75–D79 | §16, "How phase 17 built it" | Core marketing pages describe what a game module adds in core's words and link to each game's page; the homepage keeps its game screenshot, labelled; `/app/` describes the Rust screens, released the same day; `/runicnpc/` is in the header; `checkTerms.mjs` gains a pass over the built pages |
|
||||
| D80–D81 | §16, "How phase 18 built it" | A name in a screenshot is a role; the Rust captures' players are mock data |
|
||||
| D82–D83 | §15, "How the site reaches it" | `/beta` lists the demo's sign-ins as the demo publishes them; a demo deep link names its game and shows only for the games the mounted `demoGames` lists |
|
||||
|
||||
---
|
||||
|
||||
@@ -1807,9 +1809,56 @@ whether or not N3 is actioned; only one sentence changes.
|
||||
|
||||
---
|
||||
|
||||
## 15. Planned, not in scope: the demo instance
|
||||
## 15. The demo instance
|
||||
|
||||
D12. Recorded now so the IA reserves room for it and nothing has to be restructured later.
|
||||
D12. Recorded on 2026-08-19 so the IA reserved room for it and nothing had to be restructured
|
||||
later. **It exists now:** `https://demo.runicgateway.com`, built in `website` and live since
|
||||
2026-10-27. Its design of record is `docs/website/DEMO_MODE.md` (DM1-DM29), not this section, and
|
||||
it came out different from the plan below in three ways that matter to this site:
|
||||
|
||||
- **It runs Rust, not Ultima Online.** The site is the normal `website` image with the Rust module,
|
||||
linked to the org's Oxide test server. So the `/uo/…` deep links D25 wrote have nothing to open
|
||||
there.
|
||||
- **It resets every two hours, not hourly, and not by reverting a VM.** A scheduled workflow
|
||||
restores the game server from a baseline, recreates the site's database, and seeds it again
|
||||
(`DEMO_MODE.md` §7). The banner gives the next reset in UTC.
|
||||
- **Its sign-ins are generated on its host.** The passwords exist only in the demo's own `.env`
|
||||
and in what the demo publishes: with `DEMO_MODE` on, `GET /api/v1/public/settings` answers
|
||||
`demo.logins`, which is what its sign-in page lists.
|
||||
|
||||
### How the site reaches it (2026-10-28)
|
||||
|
||||
`DEMO_MODE.md` §10 step 6 says "runicgateway.com `/beta` publishes the logins". The org lead took
|
||||
two decisions to do that:
|
||||
|
||||
**D82 — `/beta` lists the demo's sign-ins as the demo publishes them.** With `demoUrl` mounted,
|
||||
`/beta` (already rendered per request) reads the demo's `GET /api/v1/public/settings` on the
|
||||
server, caches the answer for a minute, and lists each `demo.logins` row with the next wipe
|
||||
time. A copy pasted into `brand.json` was the alternative, and it is one regenerated `.env` away
|
||||
from publishing passwords that do not work. The read is this server's, not the visitor's, so D9
|
||||
and the CSP are unchanged. It never fails the page: the demo is down for a few minutes at every
|
||||
wipe, and then (or after 1.5 seconds without an answer) `/beta` links to the demo's own sign-in
|
||||
page instead, and asks again 15 seconds later. Every field is shape- and length-checked before
|
||||
it is rendered. Gate two ("somewhere to point it") reads as in place, with the demo's host name
|
||||
to type into the app's first screen. `lib/demoLogins.mjs` holds it; `test/demo.test.mjs` tests it.
|
||||
|
||||
**D83 — a demo deep link names its game, and shows only for the games the demo runs.** A link
|
||||
into a game module's pages carries `data-demo-game` after `data-demo-path`. A new mounted list,
|
||||
`demoGames` (stock `[]`), names the modules the demo runs, and `applyBrand.mjs` fills a game's
|
||||
links only for a game listed there. Core's links (`/wiki`, `/site/events`, `/site/news`) carry no
|
||||
game and follow `demoUrl` alone. The Rust features gain links into the demo's server page
|
||||
(`/rust`, and `/rust/servers/demo` with its `?tab=` for the feed, leaderboard, online, map,
|
||||
wipes and clans). `demo` is the server's id, fixed by the demo's seed fixture. UO's links stay
|
||||
in the markup and stay hidden, so a UO demo later is one more entry in the list. `checkBrand.mjs`
|
||||
holds `demoGames` to the games in `games/index.mjs` and checks that `DEEP_LINK` reads the game.
|
||||
|
||||
The `public-demo` entry in `notBuilt.mjs` is gone, because its `resolvedBy` was met.
|
||||
|
||||
**What the operator mounts:** `"demoUrl": "https://demo.runicgateway.com"` and
|
||||
`"demoGames": ["rust"]` in the site's `brand.json`, then a restart. `/beta` follows `demoUrl` on
|
||||
the next request; the prerendered pages follow both at the restart.
|
||||
|
||||
### The plan as written (2026-08-19)
|
||||
|
||||
**Shape:** a VM on the org lead's Proxmox host running the full stack — website, `module-uo`, the
|
||||
uo-link sidecar and a real ServUO shard — so an evaluator clicks one link and sees the actual
|
||||
|
||||
Reference in New Issue
Block a user