Download the PHP package digitalerase/deployer-loader without Composer
On this page you can find all versions of the php package digitalerase/deployer-loader. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download digitalerase/deployer-loader
More information about digitalerase/deployer-loader
Files in digitalerase/deployer-loader
Package deployer-loader
Short Description Autoload of vendors and autoload of deployer tasks.
License MIT
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 deployer-loader
deployer-loader
|
|
:local:
What does it do?
This package allows to:
- Register your project vendor classes to be used in deploy.php. Read "Include class loader" for more info why you should not include your project vendor/autoload.php in deploy.php.
- Load single task/setting file.
- Load multiple tasks/settings files from folders.
Installation
composer require digitalerase/deployer-loader
Usage
Include class loader ++++++++++++++++++++
If Deployer is used as phar from global install or from local in ./vendor/bin/dep (installed from deployer/dist) then
it is already including his own vendor/autoload.php. If in deploy.php file we will require vendor/autoload.php
from our project then it's like asking for trouble because we are joining two autoloads with non synchronized dependencies.
The second composer vendor/autoload.php added by us in deploy.php has priority because the composer uses the
prepend parameter of spl_autoload_register() method which adds an autoloader on the beginning of the autoload
queue instead of appending it. So classes from our project will be used before classes from Deployer phar.
The solution is to include in deploy.php the autoload.php from digitalerase/deployer-loader.
Using spl_autoload_register() it will register new closure function to find classes and it will register itself without
prepend parameter. So first classes from Deployer phar autoload will be used and if they will not exists
there will be fallback to classes from the main project vendors.
How to use it? Just include autoload at the beginning of your deploy.php (and remove vendor/autoload.php if you had one)
require_once(__DIR__ . '/vendor/digitalerase/deployer-loader/autoload.php');
After this point in code you can use all vendor classes declared in psr4 of your composer.json files.
Loading deployer tasks ++++++++++++++++++++++
The package digitalerase/deployer-loader allows you also to include single files or bunch of files from folder (recursively).
- Example for loading single file: :: new \SourceBroker\DeployerLoader\Load( [path => 'vendor/digitalerase/deployer-extended-database/deployer/db/task/db:copy.php'], [path => 'vendor/digitalerase/deployer-extended-database/deployer/db/task/db:move.php'], );
- Example for loading all files from folder recursively: :: new \SourceBroker\DeployerLoader\Load( [ path => 'vendor/digitalerase/deployer-extended-database/deployer/db/' excludePattern => '/move/' ], [ path => 'vendor/digitalerase/deployer-extended-media/deployer/media/' ], ); You can use preg_match "excludePattern" to exclude files.
Changelog
See https://github.com/digitalerase/deployer-loader/blob/master/CHANGELOG.rst
