Backups & updates
Backups
Back up the database, private/uploaded files, .env, encryption/OAuth keys, module settings and customizations. Encrypt backups, restrict access, retain an off-server copy and test restoration in isolation. Do not send production backups to support.
Updates
- Read release notes and review your installed version/customizations.
- Back up data, keys and configuration; confirm restoration.
- Test the update on a restored staging copy.
- Enter maintenance mode and stop/drain workers during the agreed window.
- Deploy matching source, dependencies and built assets. Preserve
.env, storage and existing keys. - Run only the update migrations and refresh configuration from
backend:
php artisan down
composer install --no-dev --prefer-dist --optimize-autoloader
php artisan migrate --force
php artisan optimize
php artisan queue:restart
php artisan up
- Restart other services and repeat acceptance smoke checks.
Do not run fresh-install seeders unless the release explicitly requires a reviewed data upgrade. Reverting source alone does not reverse database changes; follow the tested restore/rollback plan.