Download the PHP package davidbarratt/custom-installer without Composer
On this page you can find all versions of the php package davidbarratt/custom-installer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download davidbarratt/custom-installer
More information about davidbarratt/custom-installer
Files in davidbarratt/custom-installer
Package custom-installer
Short Description Install custom types into custom locations.
License Apache-2.0
Homepage https://github.com/davidbarratt/custom-installer
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 custom-installer
Composer Custom Type Installer
Adds a root-level custom type installer path to composer.json. Any custom type can be used to define a path the type should be installed in.
Installation
Simply require this library in your composer.json file. Typically this will be added as a dependency of the custom type to ensure that the library is loaded before the library that needs it. However, this can be added to the root composer.json, as long as it goes before any library that needs it.
Usage
The added parameter(s) are only allowed on the root to avoid conflicts between multiple libraries. This also prevents a project owner from having a directory accidentally wiped out by a library. Note: Each package will go in it’s respective folder in the order in which they are installed.
The configuration has to be added in custom-installer of composer.json's extra section. It is similar to Composer installer's installation paths.
Pattern syntax
The key of the the configuration array is the path pattern. You can use some replacement tokens:
{$name}: The name of the package (e.g.yamlofsymfony/yaml){$vendor}: The vendor of the package (e.g.symfonyofsymfony/yaml){$type}: for the composer package type (e.g.library,drupal-module)
Package filters
The value of the configuration array has to be an array. It holds the package filter for the given pattern. The pattern will be applied if any filter matches.
Package type filter
With type:[package-type] you can define a pattern per package type. You can use
any custom package type and are not limited to a predefined set.
Composer specific package types metapackage or composer-plugin will never be
handled by Custom Installer.
Example: type:custom-library for package type custom-library
Package name filter
You can specify a pattern per full package name ([vendor]/[name]).
Custom Installer will only handle a specific package if a configuration exists that also handles the package type in general.
Examples
In the example we want to make sure CKEditor and Jquery ScrollTo will be
placed in web/sites/all/libraries. Both packages are of of package type
library. In order to change the path of those packages, we must declare a
fallback for the package type library. It shall stay in the default vendor
location (as library is the default composer package type). If you do not do
that the custom installer cannot handle the single packages (ckeditor and
flesler/jquery.scrollto ) due to the way composer installer plugins work.
