Migrating to Laravel: Managing the ick
summary
Migration plan focuses on concrete steps: run CodeIgniter (PHP 5.6) and Laravel (PHP 7.2) side-by-side in containers and use nginx request split to API vs legacy so new endpoints go to Laravel while old pages stay in CI. Extract the data model into an Eloquent retrofit via Composer so both stacks share models, add Blade and Vue for front-end, use Passport tokens for auth, and automate browser checks with Laravel Dusk testing CI frontend against Laravel backend. Examples include a 9,000‑line one‑file plugin and working Dusk+Passport setups that validate the hybrid approach.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:45Who is this talk for
- 3:24Why
- 4:07Denial
- 4:57Bargaining
- 5:25Relapse
- 6:52Anger
- 7:37Initial Acceptance
- 7:59The New Love
- 8:32Infrastructure
- 10:17Control of your data model
- 14:33halloumi finder
- 15:22data models
- 16:30model feed
- 18:50migrating to Laravel
- 21:43Laravel Dusk
related talks
30mLegacy to Laravel in 30 minutes
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
49mElevating Legacy: A Case Study on the migration from Laravel 4 to 9
49mLaravel - If, how and why you should use it!
31mModern PHP development with Laravel 5.6
52mFrom Native PHP to Laravel in Production
20mhow to make the management of a league system less traumatic
10mLaravel