Dashboard — Backup

The Backup page (/backup) lets you back up your entire FitOps data directory to GitHub, restore a previous backup, and set an automatic backup schedule — all without using the CLI.

It also includes Strava webhook sync controls. Webhooks let Strava notify FitOps when activities are created, updated, or deleted, so a deployed dashboard can sync immediately instead of polling every few hours.

Connecting GitHub

Before you can back up, connect a GitHub repository:

1. Click Connect GitHub
2. Paste a GitHub Personal Access Token (PAT) with repo scope
3. Enter the target repository in owner/repo format (e.g. yourusername/fitops-backups)

FitOps stores the token locally and uses it for all subsequent backup and restore operations. To disconnect, click Remove GitHub. When GitHub is already connected, the save button is disabled until you enter a new token. Cloud backup actions are disabled while no GitHub provider is connected.

Creating a Backup

Click Create Backup Now to immediately push your current FitOps data to GitHub. The backup includes:

• The local database (fitops.db)
• All workout files (~/.fitops/workouts/)
• All note files (~/.fitops/notes/)
• Athlete settings (athlete_settings.json)

Each backup is timestamped and pushed as a GitHub Release with origin metadata. FitOps captures the database through SQLite's online backup mechanism, so the snapshot remains consistent while the dashboard is running. The dashboard skips scheduled and manual backups when the current dataset signature already matches the last successful backup, unless the backup is forced.

Viewing & Restoring Backups

The Backup History panel lists your recent backups from GitHub, newest first. Each entry shows the timestamp, origin, trigger, and dataset signature when available. HF deployments are marked as primary; local machines are marked as secondary.

Click Restore on any backup to replace your current local data with that snapshot. This is a destructive operation — your current state will be overwritten. Before installing the restored database, FitOps validates it with SQLite quick_check and clears stale WAL sidecar files so the dashboard reconnects to the restored snapshot cleanly. If the selected backup has the same dataset signature as the current database, FitOps reports the restore as a no-op.

WARNING

Restore replaces your local database and files. Make sure you don't need your current data before restoring a previous version.

Automatic Schedule

Set a backup schedule so FitOps backs up your data automatically while the dashboard is running:

• Frequency — how often to run (e.g. daily, every 6 hours)
• Time — when to run the scheduled backup

The scheduler runs in the background while the dashboard server is active. If you stop the dashboard, scheduled backups pause until you start it again. Successful GitHub uploads also run smart retention per origin, keeping recent backups plus daily, weekly, and monthly checkpoints. The schedule button is disabled when the form already matches the saved state. Change the enabled checkbox, interval, or provider to save a new schedule.

For always-on automated backups without keeping the dashboard open, use the CLI:

fitops backup schedule set --interval 24h

Strava Webhook Sync

Use Strava Webhook Sync to register the dashboard as a Strava callback target.

Webhook sync is supported for deployed FitOps dashboard servers. The callback URL must be public HTTPS and must end at the FitOps webhook endpoint:

https://your-domain.example/api/strava/webhook

Use the URL for the deployed dashboard instance Strava can reach:

Environment	Callback URL
HuggingFace Space	https://<space-host>/api/strava/webhook
Other deployed server	https://<your-domain>/api/strava/webhook
Local dashboard	Not supported for webhook sync; use polling or manual sync

localhost is only reachable from your machine, so Strava cannot call http://localhost:8888/api/strava/webhook. For local FitOps use, keep sync mode as Polling or Manual.

HF deployments created with fitops deploy hf store this callback URL automatically and register the Strava push subscription after Strava credentials are restored from backup or completed in the Space setup flow. For other deployed dashboards, use the Strava Webhook Sync panel or fitops webhooks setup.

The dashboard creates the Strava push subscription through Strava's API, but FitOps must already have your Strava app credentials saved. If the Strava developer settings page asks for an Authorization Callback Domain, enter the deployed host only, without https:// and without /api/strava/webhook.

When webhook sync is enabled:

• New Strava activities are imported automatically
• Streams and weather are fetched after import
• Activity updates refresh the local row
• Activity deletions remove the local activity and dependent cached rows
• The dashboard periodic polling loop is skipped

The Sync Mode selector controls automatic Strava sync behavior:

Mode	Behavior
Webhook	Use Strava webhooks as the automatic sync trigger
Polling	Use the periodic dashboard auto-sync fallback
Manual	Only sync when you click Sync or run the CLI

The webhook controls show no-op states directly. Webhook Active means the saved callback URL is already active in webhook mode, and Mode Saved means the selected sync mode already matches the saved mode.

See Also

• fitops backup — CLI reference for all backup commands
• fitops webhooks — CLI reference for webhook sync

← Dashboard Overview