Survival Guide | The Laravel

php artisan optimize:clear php artisan config:cache # only if in production php artisan queue:restart 90% of “broken after deploy” is cached config pointing to the wrong env. Don’t tail -200 and panic. Do this:

After any .env change, run:

It’s 9:58 PM. You just pushed what you thought was a tiny hotfix: “Update user avatar validation.” the laravel survival guide

The 10 PM Deployment Rule

Use php artisan octane:start or sail up -d with APP_ENV=local but CACHE_DRIVER=redis and QUEUE_CONNECTION=database . Simulate production locally, or the Laravel gods will simulate failure for you at 2 AM. php artisan optimize:clear php artisan config:cache # only

Add this temporarily to AppServiceProvider@boot :

Now go fix that avatar upload. And next time? Deploy at 11 AM on Tuesday. You just pushed what you thought was a

Three minutes later, your phone buzzes. Then again. Then the Slack channel erupts. “500 error on profile uploads.” “Jobs stuck in failed table.” “Why is S3 returning AccessDenied?” Welcome to Laravel after dark. Here’s your survival guide for this exact moment. Don’t open the controller. Don’t blame Redis.