Laravel 13 Deployment Checklist for a Production Website
Laravel deployment is more than uploading files. A reliable release starts with a tested build, a known PHP version, and a clear rollback path.
Before deployment, confirm the production PHP version supports the Laravel version and installed packages. Run Composer with production dependencies, ensure the application key is configured, and set APP_ENV=production and APP_DEBUG=false. Never expose .env or storage logs through the web root.
After uploading, verify the document root points to the application's public directory. Give the web-server account write access only where needed, especially storage and bootstrap/cache. Run migrations only after taking a database backup and reviewing the migration plan.
Finish by clearing and rebuilding configuration, route, and view caches as appropriate. Test login, forms, mail, queues, file uploads, and scheduled tasks. Keep the previous release or a tested backup available until the new version passes smoke tests.
- 2 Comments
- 12 Views
- Share:
2 Comment
Webguru Dev Lab 1 week ago
I would add a smoke test for the most important authenticated and public routes, not just the homepage. A successful HTTP 200 on the homepage can hide broken forms or database-backed pages.
Webguru Security Desk 1 week ago
Agreed. Also verify scheduled commands and queue workers after release; they often keep using old code or stale configuration until restarted.