Production deployment checklist

Prerequisites and authority

Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.

Production acceptance checklist

Before launch, nominate an operator and technical escalation contact. Record the selected release, edition, installer checksum and deployment addresses. Every failed check needs a tracked resolution, not an informal promise.

[ ] Supported OS/runtime and adequate disk space confirmed.
[ ] Persistent database volume and installation configuration identified.
[ ] Individual administrator access, suitable roles and sensitive-action controls checked.
[ ] License and entitled customer interfaces work.
[ ] Every router is reachable from the API and has tested provisioning.
[ ] Hotspot login, internet access, quota and expiry have been exercised.
[ ] Queued purchase begins according to its activation rule.
[ ] Multi-router concurrency and accounting pass where applicable.
[ ] Payment sandbox and stable callbacks pass before live mode.
[ ] Notification inbox and Telegram behavior are understood.
[ ] Backup schedule, separate recovery key and restore drill are recorded.
[ ] Manual update approval, maintenance notices and rollback procedure are available.
[ ] Monitoring, worker checks and incident records are assigned.

Test a host restart and a temporary router management outage during a controlled window. Check restored connectivity, outstanding operations and accounting after recovery.

Record production payment activation separately from sandbox acceptance. Never reuse test credentials unintentionally. Retain the launch record and open risks with named owners. Technical verification items in the accompanying backlog must pass before the affected guides can become release instructions.

Production deployment checklist

Prerequisites and authority

Production acceptance checklist

Related guides