# Typical Forge Deploy Script cd $site git pull origin $branch composer install --no-interaction --prefer-dist --optimize-autoloader --no-dev Maintenance mode (for zero-downtime? No. We'll fix this below) php artisan down --retry=60 || true Migrate php artisan migrate --force Clear caches php artisan optimize:clear php artisan config:cache php artisan event:cache php artisan route:cache php artisan view:cache Restart queue workers php artisan queue:restart Bring it back up php artisan up 2. The Enemy of Laravel: "php artisan down" That script above has a problem. php artisan down takes your site offline. In 2024, that is unacceptable.
By Martin Joo
DevOps isn't a job title. It's a set of practices. For a Laravel developer, that means treating your servers, queues, caches, and deploys as part of the codebase. DevOps with Laravel by Martin Joo
It does this natively. Rolling your own: Use Deployer or a custom script: # Typical Forge Deploy Script cd $site git
We need a symlink release strategy. Instead of updating the "current" folder, we deploy to a release folder and then symlink. The Enemy of Laravel: "php artisan down" That
Let’s be honest: Most Laravel tutorials stop at the point where you run php artisan serve and see "Laravel" rendered in white text on a black background. But shipping software isn't about your local environment. It’s about how reliably you can move code from your laptop to a server, run migrations without downtime, and wake up without a 3 AM alert about a full disk.