diff --git a/PLAN.md b/PLAN.md index 5fb5d14..15b2137 100644 --- a/PLAN.md +++ b/PLAN.md @@ -86,7 +86,7 @@ All values re-read from the Gitea API on **2026-08-19**, after revision 1. | **Current bundle** | **2026.08.19** (protocol 4, generated 09:05:52Z) | `installer` branch `bundles` → `current.json` | | uo-link sidecar | **v2.0.0** (2026-08-19) | release; in bundle 2026.08.19 | | Plugin overlay | **v1.0.0** (2026-08-19) | release; in bundle 2026.08.19 | -| Installer | **v0.1.0** (2026-08-07) | release | +| Installer | **v0.1.1** (2026-08-24) | release | | `module-uo` | **v1.0.1** (2026-08-19) | release | | Android app | **v0.5.0** (2026-08-08), id `com.runicgateway.app` | release; `app/build.gradle.kts` | | ServUO | **57.4** — min version, and the only version the patch tier is verified against | bundle `overlay.servuo` | @@ -909,12 +909,21 @@ Hero editor into Branding and theming, Web Bot Activity into Authentication. it is **missing from website's root `.env.example`**, the file Compose actually reads. It is present in `server/.env.example`, which is the file local development copies, which is why this has never bitten anyone in dev. The quickstart carries it, declared as an upstream omission so the - check fails the day it is fixed. + check fails the day it is fixed. **Fixed in website#163** (merged 2026-08-24), which also adds + `BOT_INTERNAL_KEY` to the README's "set at least" list — required in production even on a + deployment running no bot. The declaration did exactly what it was built to do: this repo went red + on the next run, and the entry is deleted here. - **The installer points operators at a screen that no longer exists.** It prints `/admin/shard`, and INSTALL.md §5 repeats it. Since the module-system cutover a module owns - one path segment, and the screen is **`/admin/uo/link`**, labelled *Shard (uo-link)*. Both the - binary (`installer` `main:src/sidecar.rs`) and the guide are stale; the journey documents the real - path and says the printed one does not resolve. + one path segment, and the screen is **`/admin/uo/link`**, labelled *Shard (uo-link)*. The old path + does not even 404 — the SPA sends the operator to the dashboard, so the link looks like it worked + and the four values have nowhere to go. **Fixed in installer#22** (the path is a named constant and + both handoff tests assert it) **and docs#174**, both merged 2026-08-24, and shipped in installer + **v0.1.1**. Getting there found a fourth defect, in `installer`'s release pipeline: the run for the + fix built every artifact and pushed tag `v0.1.1`, then took a `500` from `POST /releases` one + second later, leaving an orphan tag and no binaries. Re-running the workflow published it — the + failure was a race with the tag push, not a structural one — so the note here names v0.1.0 as the + version that prints the old path rather than describing the installer as currently wrong. - **The admin "Restart the server" button opens a `window.confirm`.** Its text is the honest warning that a deployment with no supervisor does not come back — which is exactly why `restart: unless-stopped` is called out as load-bearing on the install page rather than left as diff --git a/src/content/docs/docs/getting-started/connect-a-game-server.mdx b/src/content/docs/docs/getting-started/connect-a-game-server.mdx index f431c23..10b7771 100644 --- a/src/content/docs/docs/getting-started/connect-a-game-server.mdx +++ b/src/content/docs/docs/getting-started/connect-a-game-server.mdx @@ -106,10 +106,17 @@ sidebar — `/admin/uo/link`. Tick *Enable the shard integration*, paste **Base **WebSocket URL**, **Auth token** and **Protocol**, and save. The ingest client restarts immediately. -