System
Platform status
What the ops/ backup scripts recorded: the latest artifact per kind, its age, size, checksum, and how many copies retention left behind.
This screen is read-only. It never restarts, deploys, migrates, backs up or restores anything — those are YELLOW/RED actions under the security model and run from a shell through ops/. Where an action would help, the exact command to run is shown instead of a button.
Operations journal
Backups
Last database backup 6h ago
Latest per kind
| Kind | Status | Age | Size | Checksum | Retained |
|---|---|---|---|---|---|
| Database | Succeeded | 6h ago | 120 B | sha256 recorded | 2 copies |
| Environment | Never recorded | — | — | no checksum | — |
| Operations state | Never recorded | — | — | no checksum | — |
Recorded backups
| Created | Kind | Status | Artifact | Took |
|---|---|---|---|---|
| 2026-10-05 15:17 UTC | database | succeeded | /home/dome/paxx-deploy/shared/backups/database/paxx-pglite-20261005T151715Z.tar.gz | 29ms |
| 2026-10-05 15:12 UTC | database | succeeded | /home/dome/paxx-deploy/shared/backups/database/paxx-pglite-20261005T151216Z.tar.gz | 29ms |
Restores are not offered here at all — a restore is a destructive data operation (RED) and belongs in a shell with a human in front of it. Retention is applied by the backup script, not by this page.
From a shell
Taking a backup
Database backup (YELLOW):
ops/backup.sh --kind databaseEnvironment backup (YELLOW):
ops/backup.sh --kind environmentOperations state backup (YELLOW):
ops/backup.sh --kind stateRestores are deliberately absent. A restore is a destructive data operation (RED) and belongs in a shell with a human in front of it — there is no browser path to one.