URL based image manipulation

    An image has to be uploaded only once. All manipulations like resizing or cropping will be handled later, when the file is accessed via a HTTP request like this:

    Follow this few easy steps to hook the URL based image manipulation directly into your Laravel application. Once enabled the package generates a dynamic route, which forms the URL mentioned above and uses the caching system specified by your Laravel configuration.

    To use URL based image manipulation make sure you have installed the latest versions of both intervention/image and intervention/imagecache and of course a Laravel application. Refer to the installation guide of intervention/image and , if you need help on this. After installation follow a few easy steps to integrate Intervention Image into Laravel.

    2. Publish package configuration

    If everything is installed and set import the configuration file of the caching package, by running one of the following artisan commands:

    Publish configuration in Laravel 5

    $ php artisan vendor:publish

    Publish configuration in Laravel 4

    $ php artisan config:publish intervention/imagecache

    You will find the configuration file in your app directory and you may edit it to your needs:

    Essentialy that’s it. You may now list all registered routes by entering the following artisan command and check if the new route is listed correctly.

    $ php artisan route:list

    4. Define source directories

    Now you have to let PHP know, where to search for images. You may define as many directories as you like. For example define all the upload directories of your application. The application will search the directories for the submited in the route.

    ‘paths’ => array( ‘storage/uploads/images’, public_path(‘img’) )

    It makes sense to save image files with a unique filename in these directories. Otherwise the package will return the image that is found first.

    Note: For security reasons the route only accepts filenames consisting of the following characters a-z, A-Z, 0-9, - (minus), _ (underscore), / (slash) and . (dot).

    The templates are defined as names of , where you can define any manipulation operation. The configuration file comes with three different basic callbacks.

    • small - 120x90 Pixel
    • large - 480x360 Pixel

    Feel free to adapt the configuration to your needs. Especially the templates are just basic examples and they are not limited to resizing. You can use every method of intervention/image available.

    The key of the templates array in the configuration file will define the template name as the second part of the url. The value defines the name of the applied filter class.

    Accessing the original image file

    There are a the following built-in routes, you can use to bypass any template and access the original file directly.

    • original - Send HTTP response with original image file.
    • download - Send HTTP response and forces the browser to download the original image file, instead of displaying it.

    Just use the name instead of the template name.

    Filter class example

    Take a look at the following example of a template filter class to learn more about and define your own templates anywhere you like.

    After the class is loaded you can add it to the templates array in your configuration file.

    ‘templates’ => array( ‘small’ => ‘Intervention\Image\Templates\Small’, ‘medium’ => ‘Intervention\Image\Templates\Medium’, ‘large’ => ‘Intervention\Image\Templates\Large’, ‘foo’ => ‘YourApp\Filters\MyFilter’ )

    Custom image quality and format

    By default all images requested via URL based image manipulation are generated in the same format as the original with default quality. You can specify custom output settings by passing encoded data in the template class.

    2. {

    5. Image Cache Lifetime

    Once the route is accessed the first time, the image will be searched, edited according to the template and stored in the cache. So the next time you access the URL, all the GD manipulation is bypassed and the file will come directly from the cache.