Skip to content

Docs: fleet deployment plan for threshold/gain control#76

Open
pbitzer wants to merge 1 commit into
0.4.xfrom
docs/threshold-gain-deployment
Open

Docs: fleet deployment plan for threshold/gain control#76
pbitzer wants to merge 1 commit into
0.4.xfrom
docs/threshold-gain-deployment

Conversation

@pbitzer

@pbitzer pbitzer commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Deployment runbook for rolling out the server-side threshold/gain feature (PR #70, merged to 0.4.x as 01dfff7). Deploys nothing — it's a reviewed checklist for the fleet rollout.

Summary

Both changed scripts run on-demand, so no service restarts — deployment is git updates in two places.

VPS (mjol_array.py) — recommend switching monitor's checkout 0.3.x → 0.4.x. Verified safe: webgen.py (the only thing monitor's crontab runs) is byte-identical across the branches and its deps are unchanged; the only server-side diff is mjol_array.py itself. Run by a monitor login (pi can't sudo).

Sensors (ags.py) — from the 2026-07-08 read-only survey:

  • Ready now (8): mj03/04/06/08/41/42/43/50 — clean, on 0.4.x, fast-forward pull.
  • Resolve first (3): mj05 (3 dirty files), mj00 (on 0.3.x), mj02 (parked on feature/noise-alert-persistence).
  • Queued (10): unreachable units.

Includes verification steps (the deferred VPS→sensor fan-out E2E, done idempotently), rollback, and open flags.

🤖 Generated with Claude Code

Runbook for rolling out PR #70 (merge 01dfff7): VPS mjol_array.py via monitor
0.3.x->0.4.x switch (webgen verified branch-agnostic), sensor ags.py fast-forward
for the clean 8, per-unit handling for mj00/mj02/mj05, unreachable queue. No
service restarts; deploy nothing until approved.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant