Deploying Laravel from dev to production
summary
Recommends separating database, cache and storage and using Minio (S3-compatible) or external providers instead of the local driver; recommends three environments (dev, stage, production) and a minimal deploy sequence (migrations, cache, config, etc.) run at each release. Proposes Docker to keep runtimes identical, demos Git-based deploy to Heroku in under five minutes, and warns about file permissions/ownership, trusted proxies, and vague Composer versioning.
AI-written summary · about
chapters (6)
- 0:00Laravel deployment intro
- 3:36Deployment infrastructure
- 7:45PaaS technical limits
- 10:39Heroku demo
- 14:17Laravel deployment mistakes
- 16:01Q&A
related talks
42mKickass Laravel Development with Docker
41mTwelve-Factor Apps
48m12 Factors Laravel
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
49mLaravel - If, how and why you should use it!
19mDeploying Laravel Applications with Bitbucket Pipelines
37mCI/CD for Laravel Applications: Automate, Optimize and Scale
50mDeveloping for Drupal 8 with Drupal VM