Docs / Operations
Backups & restore
Snapshot the entire site and restore it in a click if something breaks — owner-only, built in, not a paid add-on.
Admin → Settings → Backups is restricted to the site's owner account, not just anyone with admin permissions — a restore rewrites the whole database, so it deliberately sits above the normal permission system.
Taking a snapshot
A snapshot captures every table — roster, ranks, events, tournaments, settings, everything except active sessions and API tokens (which are transient and shouldn't survive a restore anyway) — and stores it as a single file, kept separately from the live database so a bad restore can never delete the restore points themselves.
Restoring
Restoring wipes the current data and reloads it from the chosen snapshot, in one atomic operation — it either fully succeeds or fully fails, never leaving the site half-migrated. Before it runs, an automatic "undo" snapshot of the current state is taken first, so an accidental restore can itself be undone. The owner's own login is preserved across the restore so they're never locked out of the site they just restored.
Uploaded media files in storage aren't part of a snapshot, only the database. If you've deleted uploaded images since the snapshot was taken, restoring won't bring them back.
Why this is built in
Self-hosted software usually leaves backups as an exercise for the operator. mustr treats "someone breaks something while testing a change" as inevitable, so the safety net ships with the product rather than being a separate service to configure.