Customized Laravel Components
Customized Laravel Component Locations in Apiato
Apiato organizes Laravel's core components differently for a more modular and refined structure. Below is a guide to the default Laravel components and their locations within Apiato.
Kernels
-
Http Kernel
- Moved from
app/Httptoapp/Ship/Kernels - Renamed to
HttpKernel
- Moved from
-
Console Kernel
- Moved from
app/Consoletoapp/Ship/Kernels - Renamed to
ConsoleKernel
- Moved from
Middlewares
- Middlewares
- Relocated from
app/Http/Middlewaretoapp/Ship/Middlewares
- Relocated from
Exception Handler
- Exception Handler
- Moved from
app/Exceptionstoapp/Ship/Exceptions/Handlers - Renamed to
ExceptionsHandler
- Moved from
Service Providers
For information about the new locations of Providers, please refer to the Service Providers Documentation.
Routes
Web and API Routes
Apiato introduces an organized approach for route management, removing the default routes/web.php and routes/api.php files. To learn more about how routes are structured in Apiato, refer to the Routing Documentation.
Additional Route Files
-
Channels
- The
channels.phpfile has been moved fromroutestoapp/Ship/Broadcasts.
- The
-
Console Commands
- The
console.phpfile has been moved fromroutestoapp/Ship/Commandsand renamed toclosures.php.
- The
This new organization makes it easier to locate, maintain, and manage Apiato's core components while aligning with Laravel’s functionality.