Found in the VM test: a site's PM2 daemon started from the agent's install
job belonged to the agent's service, so stopping or updating the agent took
down every site it had installed. Before any PM2 command as a site user,
the scripts now make sure that user's daemon runs under pm2-<user> (moving
one that runs elsewhere, keeping its process list). The agent's stats no
longer start an empty daemon by asking one that isn't running. Uninstall
stops the unit before removing it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Every command takes --json (crosscode.script-report/1 on stdout, the
log on stderr) and --config (the .env values by layer, from the agent).
- .env files come from the release's env.template.json (lib/envtpl.js):
written whole on install; on deploy only new variables are appended,
and a new required one with no value stops the deploy at the checks.
- install --frp: Hub-given ports, a marked frpc.ini block (backup,
frpc verify, reload; [common] admin lines added once), no nginx.
A database on another server via DB_ADMIN_URL. Refuses an existing
database or role. Everything the run made is removed if it fails.
- restart, export (crosscode.church-export/1 ZIP), uninstall (final
backup, uploads and .env kept 30 days) and purge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>