Download the PHP package maartenstaa/laravel-41-route-caching without Composer
On this page you can find all versions of the php package maartenstaa/laravel-41-route-caching. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download maartenstaa/laravel-41-route-caching
More information about maartenstaa/laravel-41-route-caching
Files in maartenstaa/laravel-41-route-caching
Package laravel-41-route-caching
Short Description This package allows you to cache your routes definitions, thereby speeding up each request.
License BSD-3-Clause
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-41-route-caching
Laravel 4.1 and 4.2 Route Caching
This package allows you to cache routes in Laravel 4.1 and 4.2.
Installation
Using Composer, add the package to your require section.
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:
Usage
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:
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.
Why?
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.
Limitations
You cannot use this package to serialize routes using a closure, such as this:
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.
Contributing
Coding standard
All code is to follow the PSR-2 coding standard.
Unit tests
If you find a bug, feel free to send a pull request to fix it, but make sure to always include a regression test.
