App Setup & Structure
Creating a Laravel app with the installer, the slim skeleton's folders, how public/index.php boots it, and .env-driven config. Interviewers open here to see if you know where things live.
on this pageshowhide
explore
- Installation & Local Dev5 questions
- Directory Layout5 questions
- Boot & Dispatch Sequence5 questions
- Config Files & Environment6 questions
- Yearly Majors & Support6 questions
- Package Discovery & Publishing6 questions
questions
page 2 of 2When upgrading a Laravel app from 12 to 13, why is bumping laravel/framework not the whole upgrade, and what does comparing against the new skeleton add?
basics
~20 sThe framework package changes framework code, but an app's config files, bootstrap files and composer.json were copied from the laravel/laravel skeleton and do not update themselves. The upgrade guide plus a 12.x-to-13.x skeleton diff shows which of those to change.
In a Laravel queue worker serving several gym branches, why can Config::set('services.payment.key', ...) inside one job charge the next job with the wrong key?
basics
~20 sConfig::set only changes the in-memory config repository, which lives as long as the PHP process. A queue worker handles many jobs in one process and does not reset config between them, so a key set for one branch leaks into later jobs.
You run a dozen Laravel apps for a city government on mixed majors; what upgrade cadence would you set, and what trade-offs does it involve?
basics
~20 sTake minor releases continuously and schedule each app's major upgrade within a fixed window after Laravel's yearly Q1 release, so no app reaches its security-only phase unplanned; order the work by risk and exposure, not by app age.
showing 31–33 of 33