Backups and maintenance

2026-06-01 23:16:17

Keeping the site healthy.

What to back up

Asset	Method
Database	Regular mysqldump or managed host backups
Uploads	`public/uploads/` — not in git by default
Storage	`storage/` — config packages, caches, plugin data
Code	Git for core, themes, and plugins

Backup schedule

Daily — Database on production
Weekly — Full file backup including uploads
Before imports — Snapshot DB before blueprint or config sync apply

Maintenance tools

Admin → Tools → Maintenance includes:

Cache clear
Revision retention settings
Scheduled job hints and health checks
Site health warnings (slow plugins, disk space)

From CLI: composer cache:clear when deploying code updates.

Background jobs

Schedule publish, media compression, and sitemap warming rely on cron:

*/15 * * * * php bin/cms.php jobs:dispatch && php bin/cms.php jobs:work --limit=20

Updates

Apply Struxa CMS updates via the in-app updater or documented ZIP merge process. Test on staging first. Plugin and theme updates come from the catalog or manual ZIP install.

Disaster recovery

Restore database dump to empty MySQL.
Deploy matching code version from git.
Restore public/uploads/.
Run composer install and composer migrate.
Verify .env credentials and clear cache.