Download to read offline
Uploaded byDHRUV NATH
Directory Structure Changes in Laravel 5.3
The document outlines the changes in directory structure introduced in Laravel 5.3, emphasizing the removal of certain default folders like listeners, events, jobs, and policies. It explains the functionality of essential directories such as app, bootstrap, config, database, public, storage, and tests, while addressing the controversy surrounding the absence of a dedicated models directory. Overall, these changes are part of Laravel's ongoing evolution to streamline application development.
Directory Structure Changes in Laravel 5.3
- 1. Directory Structure Changes inLaravel 5.3
- 2. • Laravel iscontinuously updating its newest versions and some changes that will change the directory structure • A latest directory change coming many of the default folders will not show up until you run a command that needs them • Each version of Laravel have its directory prior to 5.3 but usually not used
- 3. • List offolders that are going away: – L i s t e n e r s – E v e n t s – J o b s – P o l i c i e s • These are directories that hold a single, more forward class structure that aren’t global to Laravel apps. Events, Jobs, Listeners, and Policies
- 4. What Is TheModels Directory? • Lots of developers are in a fix by the lack of a models directory • The lack of such a directory is mandatory • the word “models” ambiguous since it means different to many people – as the collectively of all of its business logic – as classes that reach out with a relational database
- 6. • The AppDirectory - App directory contains the main code for any application. Almost all of the classes in your app will be in the directory. • The Bootstrap Directory - This directory contains files that load the framework and compose auto loading. This directory also builds a cache directory which holds framework generated files for functionality development such as the route and services cache files.
- 7. • The ConfigDirectory - The config directory, as the name implies, holds all of your application’s configuration files. • The Database Directory - This directory comprises your database migration and seeds. Developers may also use this directory to grip a SQLite database. • The Public Directory - This directory contains the index.php file, which is the initial point for all requests arriving in your application and also houses your assets such as images, JavaScript, and CSS.
- 8. • The StorageDirectory - Storage directory holds your compiled Blade templates, sessions, caches, and other files developed by the framework. • The Tests Directory - This directory holds your computerized tests. Each test class should be suffixed with the word Test. You may run your tests using the phpunit or php vendor/bin/phpunit commands.