Routine operations
Daily and weekly checks
Section titled “Daily and weekly checks”- Confirm the process is running and connections receive handshake/ping frames.
- Review server statistics, error logs, unresolved reports, and high-impact audit entries.
- Watch disk/bucket growth and attachment failures.
- Verify the public URL, TLS certificate, and WebSocket proxy path.
Backups
Section titled “Backups”Take consistent backups of the selected database directory. Include the attachment bucket when using S3-compatible storage. Regularly restore into an isolated directory and start the binary with use to prove the backup is usable.
Configuration changes
Section titled “Configuration changes”Keep one sanitized copy of your desired settings, but never commit live secrets. Change one category at a time, validate JSON, restart when required, inspect startup counts/errors, then exercise a client handshake and representative action.
Upgrades
Section titled “Upgrades”- Back up data and attachments.
- Review protocol capability and configuration changes.
- Compile the new source without replacing the running binary.
- Test against a copy of production data.
- Stop writes, take a final backup, deploy, and watch migrations/startup.
- Verify authentication, channels, messages, uploads, moderation, and webhooks.
Keep the previous binary and a pre-upgrade backup for recovery. Do not roll data backward with an old binary after a forward-only migration unless the release explicitly supports it.