Deployment and setup
Updates and daily operations
Reviewed revisions, migrations and monitored operations.
Before updating
Read the changelog and release checklist. Choose a reviewed revision or actual published tag; do not assume a planned release exists. Take a paired database/file backup and verify isolated recovery.
Apply and check
Build and validate the revision, then use the documented Compose release flow and forward migrations. Never reset or reseed a hosted database. Check health, login, permissions and private files. Review logs before sharing so secrets and personal records are not exposed.
Rollback
Rollback is not a reverse migration. Restore the matching pre-update database/file pair and start the matching older app revision. A disposable Unix update/rollback rehearsal remains a pre-production gate.
Daily practice
Monitor service health, backup freshness, disk space and the non-identifying retention checkpoint. Retention retries exist but alert delivery is unverified. Approve institutional consent and retention policies before real athlete data. Application support stays local and sends no external email.
Downloads and release alignment
GitHub is the canonical host for versioned source archives and accepted APKs. Link exact released assets from the website; do not copy binaries into its repository. Source tarballs are not database backups or prebuilt installers. Pin the source revision and record checksums for uploaded assets. Automatic source-archive compressed bytes are not guaranteed stable.
The source tag and newer fixes under review are distinct. Merge/review and align the actual source, tag and assets before advertising an updated download; a documentation change does not publish a release.
Source and status
Reviewed on 19 October 2026. Follow the operations runbook and release checklist, updated in PR #127.