Cache and Queues

The website uses Laravel, Statamic, and optional static caching. Deployments clear and rebuild the framework caches, refresh Statamic’s stache, and restart queue workers.

Deploy-Time Cache Commands

The deploy script runs these commands inside the new release before the symlink switch:

php artisan optimize:clear
php artisan statamic:stache:refresh
php artisan config:cache
php artisan route:cache
php artisan view:cache

After the release is live, it runs:

php artisan queue:restart

If static warming is enabled for the environment, it then runs:

php please static:warm

Manual Cache Refresh

Use these commands when content or configuration looks stale:

php artisan cache:clear
php artisan statamic:stache:refresh
php please static:warm

Use the static warm command only when static caching is enabled for the environment. If a stale page affects only dynamic or uncached content, start with cache:clear and statamic:stache:refresh.

Queue Worker

The local Solo process definition includes:

php artisan queue:work

Production process supervision should keep the queue worker running and restart it after deploy. The deploy script uses php artisan queue:restart, which asks existing workers to restart cleanly after their current job.

If queued work stops processing:

1. Check that a queue worker process is running.
2. Check recent Laravel logs.
3. Restart the worker through the process supervisor.
4. Re-run the failed action or let the queue retry according to Laravel’s queue configuration.

Logs and Health Checks

Useful local commands:

php artisan pail
tail -n 50 -f storage/logs/laravel.log

Useful deploy checks:

• current points at the expected release.
• current/.env points at shared environment configuration.
• current/storage points at shared storage.
• current/public/assets points at shared public assets.
• current/users points at shared Statamic user files.
• Queue workers have restarted after deploy.
• Static warm completed if enabled for the environment.

Backups

Backups must cover:

• the application database;
• shared Laravel storage;
• shared public assets;
• shared Statamic user account files.

The exact backup host, schedule, credentials, and restore transcripts are private operational details and should stay outside the public docs.