docs(installer): record Phase 2 as built — sidecar install and service #91
Reference in New Issue
Block a user
No description provided.
Delete Branch "docs/installer-phase2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
Docs half of installer#5 — Phase 2 of
installer/PLAN.mdis built and on the installer repo'sedgebranch, so the design of record and the operator guide move with it.PLAN.md
edge → maincutover now follows Phase 3, not Phase 2 —INSTALL.md§4 describes the patch tier as part of the run, and a first release that answers "not implemented" to all of it is the same half-capable binary that kept Phase 1 offmain.sc.exeoffers no per-service environment, only a machine-wide one that every process on the host inherits and that outlives an uninstall.--verifyrunning no part of the sidecar half, the protocol check against the installed binary,RUNICGATEWAY_STATE_DIRrelocating the binary and suppressing service registration, degrading to a printed recipe with no root/LocalSystem fallback, and the token never enteringinstall.json.sc create, as recommended — plus the service identity the recommendation did not anticipate.INSTALL.md
sidecar.toml's permissions are restricted because it holds the auth token.--configinbinPath(single-quoted, so PowerShell keeps the inner quotes the SCM needs),obj=for the virtual account, theicaclslockdown before and the grants after, and no machine-wide environment variables.How it was tested
Prose only. Every claim added here was checked against the code it describes, and the behaviour it documents was exercised end to end on Windows — see the testing section of installer#5.
Checklist
AI-assisted contributions (required)
Claude Code. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with aCo-Authored-Bytrailer.License