Cerynix Support
Operations runbook

Upgrade Cerynix safely

The updater automates download, rebuild and validation. Production change control, backup verification and schema-aware recovery remain operator responsibilities.

1

Prepare

  • Announce a maintenance window and stop user changes.
  • Record the current version and confirm adequate disk space.
  • Run scripts/backup.sh, copy the encrypted result off-box and complete a restore drill with the off-box age identity.
  • Keep the installer-created application snapshot and database backup until acceptance is complete.
2

Run and validate

production host
cd ~/cerynix-onprem
./install.sh --update

Require both Update complete and SELF-TEST: PASS. Then verify login, health, a read/write workflow, evidence access, reports and external integrations.

3

If validation fails

ImportantThe installer attempts to restore the previous application files when its self-test fails. It does not reverse database migrations.

If no migration ran, the application snapshot may be sufficient. If a migration ran—or you are unsure—do not assume old code is compatible with the new schema. Preserve logs and current data, keep the service in maintenance, and follow the disaster-recovery runbook using the pre-upgrade backup.

4

Close the change

Monitor logs and health, record the deployed version and evidence of validation, then retain recovery artifacts according to policy. Remove them only after the rollback window has closed.

← SupportDisaster recovery →