Tournament night is busy enough. Remembering to export and back up your data shouldn’t be part of the job.
v5.0.6 adds automatic server backup — one checkbox in Global Settings and every completed tournament is saved to disk. Configure a remote server and it’s backed up there too. The data survives browser cache clears, device changes, and the walk home from the venue.
Automatic Backup
A new setting in Global Settings → Server Settings: “Automatically backup tournaments on completion.”
When enabled, the tournament JSON is saved to the server’s /tournaments/ directory the moment a tournament is completed. No manual step, no file picker, no remembering. Backed up tournaments are available from any computer connecting to the server.
Remote Backup
Configure a remote NewTon instance in Global Settings → Remote Backup:
Remote server URL — the address of another NewTon server
When configured, auto-backup sends to both the local server and the remote server. The remote upload uses a relay endpoint (api/relay.php) — PHP forwards the request server-side, so basic auth works naturally without CORS issues.
The relay requires both instances to run with the REST API enabled (Docker deployment).
Backup to Server Button
The “Upload to Server” button in Tournament Setup is now “Backup to Server” and opens a modal with source choice (Active tournament or from file) and destination info. One click backs up to all configured destinations.
Everything Else
Shared Tournaments — collapsed by default. “Show All” to expand. Tournaments not in localStorage show “Import”, those already present show “Re-import”.
Navigation reorder — Analytics now comes before Global Settings.
Server ID display — Global Settings shows the auto-generated Server ID (read-only).
Analytics dates — YYYY-MM-DD format throughout, consistent with the rest of the app.
Analytics format label — match list header spells out “Double Elimination” / “Single Elimination”.
Backfill format fix — backfilled matches now include the best-of value.
Requirements
All backup features require the REST API to be enabled — this means running NewTon via Docker with NEWTON_API_ENABLED=true (the default). The “Backup to Server” button only appears when the API is detected. Plain HTML deployments are unaffected — export to file remains the backup path.
Migration
No migration required. All new settings default to off — current behaviour is preserved. The auto-backup checkbox must be explicitly enabled. Remote backup fields are empty by default.
NewTon DC Tournament Manager v5.0.6 — Because Backups Shouldn’t Be Homework.