RADIO CP - Backups

Backup and restore centre

Protect your station widgets, content, schedules, presenters and settings.

Create downloadable RADIO CP JSON snapshots now, plan scheduled server backups later, and prepare backend routes for database, uploads and AzuraCast integration backups.

Backups

0

Saved demo snapshots

Last backup

—

No backup yet

Schedule

Manual

Not scheduled

Snapshot size

0 KB

Latest export size

Create backup

Backup name

Backup type

DestinationOnly browser/local export works in this static prototype. Other destinations are backend-ready placeholders.

Include sections

Station settings Widgets + embeds Schedules DJs / presenters News, RSS + site Rewind + podcast metadata Requests + sponsors Analytics snapshots

Encrypt

Retention

Schedule automatic backups

Backup history

Name	Type	Destination	Size	Status	Created

Restore from backup

Safety: restore actions in this prototype import JSON into browser localStorage. In production, restore should create a server-side restore point first.

Upload RADIO CP backup JSON

Choose a backup JSON file to preview what it contains.

Production backend blueprint

A production RADIO CP backup service should back up the database, uploaded media/artwork, widget configs, generated website files, podcast RSS settings, and encrypted AzuraCast connection records. Public widgets should keep working while a backup runs.

POST /api/radio-cp/backups/run
GET  /api/radio-cp/backups
GET  /api/radio-cp/backups/{backup_id}/download
POST /api/radio-cp/backups/{backup_id}/restore
POST /api/radio-cp/backups/import
PUT  /api/radio-cp/backups/schedule

Suggested backup contents:
- PostgreSQL / MySQL database dump
- uploads/: logos, fallback images, presenter photos, sponsor artwork
- podcast and rewind metadata
- website-builder generated pages
- widget presets and embed configuration
- RSS feed configuration and cached thumbnails
- encrypted AzuraCast base URL, station shortcode and token reference
- audit log of who created/restored each backup