remote/database.sh runs on the host (over ssh's stdin) after .env and before
broker and engine:
- no bundled database: nothing to do;
- the volume it already uses: plain `up -d --wait`, recreated only on a changed
image or definition, so a new PostgreSQL minor release arrives with the next
deploy;
- another volume (a new major version): a normal deploy stops there, nothing
changed; with --infra-db the engine stops, the old database is counted and
dumped (kept in ~/netork/backups), the new container comes up on the new
volume, restore, ANALYZE, counts and Alembic revision must match. The old
volume stays, and deploying the previous version with --infra-db switches
back onto it without a restore.
Checked on .50 in reconcile mode: the running postgres:16 container stayed as
it was. README describes the steps and the way back.