astrbot_plugin_private_comp.../ops
YokiiroBW 1bd4821538 chore: script the deployment discipline
There was no shell script anywhere in either repo, so every deployment was
typed by hand and every deployment re-exposed the same pitfalls: rollback
copies left in the plugin scan directory, wrong ownership, stale pycache,
deploying the companion before memory, and a rollback pointer left aimed at an
older backup.

ops/deploy-plugin.sh fixes the order: local test gate, remote backup with the
LATEST_M6 pointer updated, stop, memory before companion (the companion probes
the memory bridge at startup and caches a negative result if the peer is
absent), ownership and modes, a scan-directory residue check that exits
non-zero on any .old/.new/.bak, remote compileall with PYTHONPYCACHEPREFIX,
start, then verification of service state and plugin-level error count.

The ownership rule was documented two ways -- root:root in the errata,
astrbot:astrbot in the M6.1.8 record. The service runs as User=astrbot, so
astrbot:astrbot is correct and the script now says so in a comment.

Also noted, in the script and the errata: QQ's official platform rate-limits
bot session starts, and restarting eight times within an hour made the
qq_official adapter fail to log in. Batch deployments should batch restarts.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 05:42:03 +08:00
..
deploy-plugin.sh chore: script the deployment discipline 2026-07-27 05:42:03 +08:00