Package Data | |
---|---|
Maintainer Username: | MaartenStaa |
Maintainer Contact: | maartenstaa@gmail.com (Maarten Staa) |
Package Create Date: | 2015-01-24 |
Package Last Update: | 2016-05-10 |
Language: | PHP |
License: | BSD-3-Clause |
Last Refreshed: | 2024-11-30 15:25:26 |
Package Statistics | |
---|---|
Total Downloads: | 340,348 |
Monthly Downloads: | 1,333 |
Daily Downloads: | 16 |
Total Stars: | 25 |
Total Watchers: | 7 |
Total Forks: | 11 |
Total Open Issues: | 1 |
This package allows you to cache routes in Laravel 4.1 and 4.2.
Using Composer, add the package to your require
section.
{
"require": {
"maartenstaa/laravel-41-route-caching": "dev-master"
}
}
Run composer update
. Next, open up your app/config/app.php
configuration file
and add the service provider at the end of the providers section:
return array(
// ...
'providers' => array(
// ...
'MaartenStaa\Routing\RoutingServiceProvider',
),
);
In your app/routes.php
file, or any other file you use that defines routes, wrap
the definition of your routes in a call to Route::cache
as follows:
Route::cache(__FILE__, function() {
// Define your routes here.
});
This package will save the routes defined in the closure, and write them to your
cache. On any subsequent requests, it will figure out the closure will not have
to be executed, and it will load the routes from your cache instead. Since you're
passing it the name of the file that defines the routes (__FILE__
), the script
will automatically detect when the file has been modified. In other words, you do
not need to clear your cache after adding a new route.
Through profiling, I found that defining many routes (in my case 100+) took a significant time on each request - time that would have been better spent preparing the response for the user.
Caching these routes significantly reduces overhead.
You cannot use this package to serialize routes using a closure, such as this:
Route::get('/', function () {
return 'Hello, world!';
});
You can only use it to serialize routes to a controller. If your app/routes.php
file has both, you can of course put all controller routes in a cache
call,
and any routes that use closures outside of it.
All code is to follow the PSR-2 coding standard.
If you find a bug, feel free to send a pull request to fix it, but make sure to always include a regression test.