M32: clarify deployment source evidence
MobilityOps acceptance / backend (push) Canceled after 0s
MobilityOps acceptance / frontend (push) Canceled after 0s

This commit is contained in:
NuklearRabbit
2026-08-10 21:19:27 +02:00
parent b44915ff35
commit be33b46228
2 changed files with 3 additions and 3 deletions
+2 -2
View File
@@ -2728,8 +2728,8 @@ evidence yet."
## M32 — M31 production acceptance and integration proof (2026-08-10)
- Pushed M31 to Gitea `master`, deployed the committed runtime, and refreshed the exact
server source marker to `eecfcb4b79a3dd0d36d5b85580e09b9b0432e479`. The verified
- Pushed M31 to Gitea `master`, deployed runtime commit `cb7edb0`, and refreshed the
server source marker to the current evidence HEAD on `master`. The verified
pre-deployment custom-format backup is
`backups/postgres/mobilityops-20260810T185833Z.dump`; its SHA-256 and
`pg_restore --list` both passed. Alembic remains `b913a72e8c14 (head)`.
+1 -1
View File
@@ -2,7 +2,7 @@
## Accepted implementation
- Runtime commit: `eecfcb4b79a3dd0d36d5b85580e09b9b0432e479` (`master`; runtime code from `cb7edb0`).
- Deployment source marker: current `master`; the application image was built from runtime commit `cb7edb0` and the following commits contain acceptance/evidence only.
- Live demo: `http://192.168.10.150:1236` — public passwordless synthetic demo.
- Deployment: Unraid `/mnt/user/appdata/mobilityops`, Compose project `mobilityops`.
- Database migration: `b913a72e8c14 (head)`.