wtclaude
dff4ad41c9
All checks were successful
PR Checks / rust-gates (pull_request) Successful in 1m31s
Adds the Rust crate at the repo root and implements `install` end to end for the overlay half of a deployment: resolve the published bundle, find and validate the ServUO root, refuse to deploy under a running shard, sync the plugin overlay, and record what was deployed in install.json. `doctor`, `update` and `uninstall` parse and answer with the phase they arrive in rather than "unrecognized command", and the run states plainly that the uo-link sidecar (Phase 2) and the patch tier (Phase 3) were not installed — `--patches` in particular reports REQUESTED BUT NOT APPLIED, since a quiet completion would be read as a patched shard. Landing on `edge` rather than `main`: release.yml publishes a binary on every push to main, and an installer that deploys the overlay but cannot install the sidecar is not something to hand an operator. pr-checks.yml now gates PRs into edge on the same rules, so the branch the work happens on is not the ungated one. Notable decisions, all documented in docs/installer/PLAN.md §5 Phase 1: - The code lives in a library called `rgdeploy` with a thin binary that keeps the published name. Windows' UAC installer detection refuses to launch an unsigned executable whose file name contains "install" (os error 740), and Cargo names test harnesses after their target — so a target under that name makes `cargo test` unrunnable on Windows. - The running-shard check matches processes by path, not by process name: on Linux a live shard is `mono`/`dotnet` with ServUO.exe as an argument, and a name match would report "not running" for a shard that is running. - install.json records a state (`deployed` / `kept-operator-modified`), not the run's verb, so an unchanged re-run produces an identical record and writes nothing. - The Bridge.cfg keep rule compares against the hash the installer last deployed, not the last hash it saw — otherwise a kept file is overwritten on the very next run. - Downloads are verified against the bundle's SHA256 while being written, then every extracted file is re-hashed against the release's own manifest.json, whose protocol and version are cross-checked against the bundle. Verified against a real ServUO 57.4 tree and end to end into a scratch tree: 24 files deployed, an unchanged re-run that writes nothing, an edited Bridge.cfg kept across repeated runs while code files are overwritten, bundle pinning, and a refusal with a shard running out of the tree. Co-Authored-By: Claude <noreply@anthropic.com>
60 lines
2.5 KiB
TOML
60 lines
2.5 KiB
TOML
[package]
|
|
name = "runicgateway-installer"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
description = "Deployment tool for Runic Gateway: syncs the ServUO plugin overlay, installs the uo-link sidecar, and records what it deployed."
|
|
license = "GPL-3.0-or-later"
|
|
repository = "https://gitea.whitlocktech.com/RunicGateway/installer"
|
|
|
|
# The published binary keeps the name PLAN.md §3 and INSTALL.md give it. The library it is built
|
|
# from does not share that name on purpose: Windows' UAC installer detection refuses to launch an
|
|
# unsigned executable whose file name contains "install" (`os error 740`), and Cargo names test
|
|
# harnesses after their target — so a target called `runicgateway_installer` makes `cargo test`
|
|
# unrunnable on Windows. `test = false` keeps Cargo from building a harness under the binary's
|
|
# name; all the code, and all the tests, live in the library. See src/lib.rs.
|
|
[lib]
|
|
name = "rgdeploy"
|
|
path = "src/lib.rs"
|
|
|
|
[[bin]]
|
|
name = "runicgateway-installer"
|
|
path = "src/main.rs"
|
|
test = false
|
|
|
|
[dependencies]
|
|
# Blocking HTTP over a pure-Rust TLS stack (rustls + ring + webpki-roots). The
|
|
# release cross-compiles to x86_64-pc-windows-gnu through MinGW, where anything
|
|
# linking OpenSSL turns a one-line build into a toolchain project — and this tool
|
|
# makes a handful of sequential requests, so an async runtime would be overhead
|
|
# with nothing to overlap.
|
|
ureq = "3.3"
|
|
|
|
# Overlay releases ship as gzipped tar. flate2's default backend is miniz_oxide
|
|
# (pure Rust), so it cross-compiles with no C dependency of its own.
|
|
flate2 = "1"
|
|
tar = "0.4"
|
|
|
|
# SHA256 is the entire trust anchor for these deliberately unsigned artifacts
|
|
# (PLAN.md §3), which makes this load-bearing rather than a nicety.
|
|
sha2 = "0.11"
|
|
|
|
serde = { version = "1", features = ["derive"] }
|
|
serde_json = "1"
|
|
|
|
# RFC 3339 timestamps for install.json. Same feature set link's sidecar uses.
|
|
chrono = { version = "0.4", default-features = false, features = ["std", "clock"] }
|
|
|
|
# Refusing to deploy under a running shard is a correctness requirement, not a
|
|
# courtesy: ServUO holds Scripts.dll open and rewrites Saves/ on exit. Only the
|
|
# `system` feature is wanted — disks, networks and users are not our business.
|
|
sysinfo = { version = "0.38", default-features = false, features = ["system"] }
|
|
|
|
# Error plumbing, as in link's sidecar. Every failure here is read by an operator
|
|
# rather than matched on, so a chain of `.context()` strings is the whole
|
|
# requirement — the value is that "failed to write install.json" arrives with the
|
|
# path and the OS error attached instead of alone.
|
|
anyhow = "1"
|
|
|
|
[profile.release]
|
|
opt-level = 2
|