![]() The HTTP kernel extends the Illuminate\Foundation\Http\Kernel class, which defines an array of bootstrappers that will be run before the request is executed. For now, let's just focus on the HTTP kernel, which is located in app/Http/Kernel.php. These two kernels serve as the central location that all requests flow through. Next, the incoming request is sent to either the HTTP kernel or the console kernel, depending on the type of request that is entering the application. The first action taken by Laravel itself is to create an instance of the application / service container. The index.php file loads the Composer generated autoloader definition, and then retrieves an instance of the Laravel application from bootstrap/app.php. Rather, it is a starting point for loading the rest of the framework. The index.php file doesn't contain much code. All requests are directed to this file by your web server (Apache / Nginx) configuration. The entry point for all requests to a Laravel application is the public/index.php file. If you don't understand all of the terms right away, don't lose heart! Just try to get a basic grasp of what is going on, and your knowledge will grow as you explore other sections of the documentation. By getting to know the overall framework better, everything feels less "magical" and you will be more confident building your applications. The goal of this document is to give you a good, high-level overview of how the Laravel framework works. When you understand how your development tools function, you feel more comfortable and confident using them. When using any tool in the "real world", you feel more confident if you understand how that tool works. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |