Download the PHP package imscp/composer-installers without Composer
On this page you can find all versions of the php package imscp/composer-installers. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download imscp/composer-installers
More information about imscp/composer-installers
Files in imscp/composer-installers
Package composer-installers
Short Description i-MSCP composer installers
License LGPL-2.1-only
Homepage https://www.i-mscp.net/
Informations about the package composer-installers
Composer installers for i-MSCP
This is for i-MSCP composer package authors to require in their composer.json
.
It will install their package to the correct location based on the specified
package type.
Current supported installers and package types
Installer | Types |
---|---|
i-MSCP | imscp-plugin imscp-theme imscp-tool |
Roundcube | roundcube-plugin |
Example composer.json
This is an example for the i-MSCP PhpMyAdmin composer package. The only
important parts to set in the composer.json file are "type": "imscp-tool"
which describes what package is and "require": { "imscp/composer-installers": "^1.0" }
which tells composer to load the custom installers.
This would install the package to the gui/public/tools/phpmyadmin/
path.
Custom install paths
i-MSCP developers and/or administrators can override the install paths in
different ways, using the installer-paths
extra in the composer.json
of the
i-MSCP instance :
Per package basis
would install both the konzeptplus/imscp-api
and imscp/dns-provisioning
packages into the custom/path/{$name}/
path.
Per package type basis
would install any package of type imscp-plugin
into the
custom/path/{$name}/
path.
Per vendor basis
would install any package provided by the konzeptplus
vendor into the
custom/path/{$name}/
path.
In all the above cases, the following variables are available for use in paths:
{$name}
: Package name{$vendor}
Vendor name{$type}
Package type
Custom install name
As a package author, you can name it differently when installed by using the
installer-name
extra in the package composer.json
.
If you have a package named imscp/roundcube
of typeimscp-tool
, it would
be installed in the gui/public/tools/roundcube
path. To provide this
package as default Webmail, you need override its name as follows:
By doing so, the package would be installed in the gui/public/tools/webmail
path.
Disabling installers
There may be time when you want to disable one or more installers from
imscp/composer-installers
. For instance, if you are managing a package that
uses a specific installer that conflicts with imscp/composer-installers
but
also have a dependency on a package that depends on imscp/composer-installers
.
Installers can be disabled by specifying the extra installer-disable
property. If set to true
, "all"
, or "*"
all installers will be disabled.
Otherwise a single installer or an array of installers may be specified.
Note: Using a global disable value (true
, "all"
, or "*"
) will take
precedence over individual installer names if used in an array. The example
below will disable all installers.
All versions of composer-installers with dependencies
composer-plugin-api Version ^1.1