Backups & upgrades

Backups

All meets and history live in one database.

• SQLite: the database is a single file. Back it up by copying that file when the app is idle (the database uses WAL mode, so also capture the -wal and -shm sidecar files, or checkpoint first). Keep periodic copies off the machine.
• Postgres: use your provider’s snapshots or pg_dump on a schedule.

Upgrades

The schema is versioned with migrations that run on startup, so upgrading is usually: stop the app, deploy the new version, start it (migrations apply automatically).

• Always back up first, especially before a release that includes schema changes.
• Migrations are designed to be forward-only — restore from backup rather than hand-rolling a downgrade.

Desktop

The desktop app keeps its database in the OS app-data directory; back that file up the same way as any SQLite database.