docs: point deploy docs at Sando, retire deploy.sh references
Policy is always Sando, never deploy.sh, but README/CONTRIBUTING across the
server and mnw-cli still pointed a fresh reader at deploy/deploy.sh as the
production path (and advertised cargo zigbuild cross-compilation, a convention
violation). Repoint all six locations at the Sando controller; label the
scripts as retained cutover references only.
Co-Authored-By
Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-07-23 01:43 UTC
./deploy/deploy.sh --quick # Binary only + restart
474
-
./deploy/deploy.sh --config # Config files only
475
-
```
470
+
Deploys go through Sando, the pipeline controller (`sandod`, on fw13), which
471
+
builds the server natively, runs the gate tiers, and swaps the release on the
472
+
prod host. Never deploy by hand: no `deploy.sh`, no `scp`, no building on the
473
+
prod box. The operator procedure lives in `../sando/deploy/README.md`.
476
474
477
-
Cross-compiles to x86_64-unknown-linux-gnu via `cargo zigbuild`. Version is read from `Cargo.toml` and compiled into the binary via `env!("CARGO_PKG_VERSION")` for Sentry release strings. Bump the version in `Cargo.toml` before every production deploy.
475
+
The version is read from `Cargo.toml` and compiled into the binary via
476
+
`env!("CARGO_PKG_VERSION")` for Sentry release strings. Bump the version in
477
+
`Cargo.toml` before every production deploy.
478
+
479
+
`server/deploy/deploy.sh` is a retained cutover reference, not a supported path.