Content Delivery Network (CDN) Package for Laravel
breachaware/laravel-cdn is a Laravel package for content delivery network (cdn) package for laravel.
It currently has 0 GitHub stars and 95 downloads on Packagist (latest version v0.0.1).
Install it with composer require breachaware/laravel-cdn.
Discover more Laravel packages by breachaware
or browse all Laravel packages to compare alternatives.
Last updated
THIS PACKAGE IS STILL IN DEVELOPMENT. DO NOT USE THIS PACKAGE IN PRODUCTION!
The package allows you to upload your static assets to AWS S3 with a single Artisan command. Optionally, you may configure a CloudFront or CloudFlare URL.
to upload their assets (or any public file) to a CDN with a single artisan command. And then it allows them to switch between the local and the online version of the files.
This project has been forked from https://github.com/publiux/laravelcdn, which was forked from https://github.com/Vinelab/cdn. All credit for the original work goes to Vinelab and publiux.
master).Require breachaware/laravel-cdn in your project:
composer require breachaware/laravel-cdn
'providers' => array(
//...
BreachAware\LaravelCdn\CdnServiceProvider::class,
),
'aliases' => [
//...
'CDN' => BreachAware\LaravelCdn\Facades\CdnFacade::class,
],
If you are using Laravel 5.5 or higher, there is no need to register the service provider or alias as this package is automatically discovered.
Publish the package config file:
php artisan vendor:publish --provider "BreachAware\LaravelCdn\CdnServiceProvider"
This package can be configured by editing the config/cdn.php file. Alternatively, you can set many of these options in as environment variables in your '.env' file.
Set your AWS Credentials and other settings in the .env file.
Note: you should always have an .env file at the project root, to hold your sensitive information. This file should usually not be committed to your VCS.
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
Set the CDN URL:
'url' => env('CDN_Url', 'https://s3.amazonaws.com'),
This can altered in your '.env' file as follows:
CDN_Url=
To load your LOCAL assets for testing or during development, set the bypass option to true:
'bypass' => env('CDN_Bypass', false),
This can be altered in your '.env' file as follows:
CDN_Bypass=
'cloudfront' => [
'use' => env('CDN_UseCloudFront', false),
'cdn_url' => env('CDN_CloudFrontUrl', false)
],
This can be altered in your '.env' file as follows:
CDN_UseCloudFront=
CDN_CloudFrontUrl=
For now, the only CDN provider available is AwsS3. Although, as DO natively support the AWS API, you can utilise it by also providing the endpoint, please see the cdn.php config for more info. This option cannot be set in '.env'.
'default' => 'AwsS3',
'aws' => [
's3' => [
'version' => 'latest',
'region' => '',
'endpoint' => '', // For DO Spaces
'buckets' => [
'my-backup-bucket' => '*',
]
]
],
'buckets' => [
'my-default-bucket' => '*',
// 'js-bucket' => ['public/js'],
// 'css-bucket' => ['public/css'],
// ...
]
Specify directories, extensions, files and patterns to be uploaded.
'include' => [
'directories' => ['public/dist'],
'extensions' => ['.js', '.css', '.yxz'],
'patterns' => ['**/*.coffee'],
],
Specify what to be ignored.
'exclude' => [
'directories' => ['public/uploads'],
'files' => [''],
'extensions' => ['.TODO', '.txt'],
'patterns' => ['src/*', '.idea/*'],
'hidden' => true, // ignore hidden files
],
'acl' => 'public-read',
'metadata' => [ ],
'expires' => gmdate("D, d M Y H:i:s T", strtotime("+5 years")),
'cache-control' => 'max-age=2628000',
You can always refer to the AWS S3 Documentation for more details: aws-sdk-php
You can 'push' your assets to your CDN and you can 'empty' your assets as well using the commands below.
Only changed assets are pushed to the CDN. (THanks, )
Upload assets to CDN
php artisan cdn:push
You can specify a folder upload prefix in the cdn.php config file. Your assets will be uploaded into that folder on S3.
Delete assets from CDN
php artisan cdn:empty
CAUTION: This will erase your entire bucket. This may not be what you want if you are specifying an upload folder when you push your assets.
There are two primary options when retrieving the CDN URL of a static asset:
Use the CDN facade to call the CDN::asset() function.
Note: the asset works the same as the Laravel asset it start looking for assets in the public/ directory:
{{ CDN::asset('css/app.css') }} // example result: https://cdn.yourdomain.com/css/app.css
{{ CDN::asset('js/app.js') }} // example result: https://cdn.yourdomain.com/js/app.js
Use the CDN facade to call the CDN::mix() method.
Note: the mix method works by parsing the mix-manifest.json file that is generated by webpack, the same as Laravel Mix.
{{ CDN::mix('css/app.css') }} // example result: https://cdn.yourdomain.com/css/app.css?id=2f7c00b6f09552c3f0ce
{{ CDN::mix('js/app.js') }} // example result: https://cdn.yourdomain.com/js/app.js?id=dbd07402af699be7a212
To use a file from outside the public/ directory, anywhere in app/ use the CDN::path() function:
{{CDN::path('private/something/file.txt')}} // example result: https://css-bucket.s3.amazonaws.com/private/something/file.txt
To run the tests, run the following command from the project folder.
$ ./vendor/bin/phpunit
Please request support or submit issues via Github
Please see CONTRIBUTING for details.
If you discover any security related issues, please do not raise a Github issue. Instead, please email [email protected] with the details of the vulnerability.
The MIT License (MIT). Please see License File for more information.
Note: The version history has been reset since forking from the original package.