docs(installer): record Phase 1 as built
PLAN.md moves from "Phase 0 complete, no code exists" to "Phase 1 built, on edge", and the Phase 1 section gains an "As built" block in the same shape as the Phase 0 entries — covering the decisions that were not already settled by the design: why the crate lands on `edge` instead of `main`, why the library target is not named after the binary (Windows UAC installer detection makes `cargo test` unrunnable under that name), the dependency choices that follow from the MinGW cross-build, path-based rather than name-based shard-running detection, reading ServUO's version from Server/AssemblyInfo.cs, and the two rules the smoke test corrected — install.json recording a state rather than the run's verb, and the Bridge.cfg keep comparing against the last hash deployed rather than the last hash seen. INSTALL.md gains the same status note and one troubleshooting row: Windows elevates the binary on launch because its file name contains "install", which is expected and needs no action beyond running from an elevated shell. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -5,6 +5,11 @@ installation and connects it to a Runic Gateway website.
|
||||
|
||||
> **Status: the installer binary is not released yet.**
|
||||
>
|
||||
> Phase 1 — the installer core: bundle resolution, ServUO detection, the overlay sync and
|
||||
> `install.json` — is built and lives on the installer repo's `edge` branch. It is deliberately not
|
||||
> released: a binary that deploys the overlay but cannot yet install the sidecar would not do what
|
||||
> this guide describes. The first release follows Phase 2.
|
||||
>
|
||||
> Everything it installs *is* released and published — the sidecar, the plugin overlay, and the
|
||||
> [bundle manifest](https://gitea.whitlocktech.com/RunicGateway/installer/src/branch/main/bundles/current.json)
|
||||
> that names the checked combination of the two. This guide is the operator-facing contract those
|
||||
@@ -496,6 +501,7 @@ The report is also written to a file, so it survives the scrollback.
|
||||
|
||||
| Symptom | Cause and fix |
|
||||
|---|---|
|
||||
| **Windows asks for Administrator as soon as you launch it** | Expected, and it needs Administrator anyway. Windows applies *installer detection* to unsigned executables whose file name contains `install` and elevates them before the program starts. Run it from an already-elevated PowerShell and you will not see the prompt. |
|
||||
| **"ServUO is running — stop it before installing"** | Correct, and not overridable. `ServUO.exe` locks `Scripts.dll` and rewrites `Saves/` on exit; deploying underneath it corrupts one or both. Stop the shard, install, start it again. |
|
||||
| Shard boots clean but nothing reaches the site | The classic silent failure: ServUO ignores the script build's exit code and reloaded a **stale `Scripts.dll`**. Run `dotnet build Scripts/Scripts.csproj -c Release -p:Platform=x64` and read the errors it prints. |
|
||||
| `[bridge status` says `connected=False` | The sidecar is not listening on `127.0.0.1:7788`. Check the service is running, and that `[shard] bind` in `sidecar.toml` matches `Host`/`Port` in `Bridge.cfg`. |
|
||||
|
||||
Reference in New Issue
Block a user