Extend Pacemaker Community Edition with additional libraries and vendors
For more complex projects, additional libraries may get needed.
Pacemaker Community Edition Console Tool uses Symfony DI container. Therefore, it is necessary to register other libraries by adding them to the configuration file.
|
When developing an extension library, the Symfony DI configuration must get provided |
Extension libraries
Is the Pacemaker Community Edition Console Tool being installed as a Composer library and a Magento 2 installation?
The easiest way to register an additional extension is to create and add a snippet, e.g.,
<custom-configuration-dir>/extension-libraries.json
, containing the library names needed
<custom-configuration-dir>/extension-libraries.json
{
"extension-libraries" : [
"techdivision/import-product-magic360"
]
}
Only if the extension library uses the same Composer autoloader as Pacemaker Community Edition Console Tool it is possible to include the extension library. When installing with the PHAR version of Pacemaker Community Edition, it is required to use the
|
Additional vendor directories
Only if the extension library uses the same Composer autoloader as Pacemaker Community Edition Console Tool it is possible to include the extension library.
PHAR installation
When installing with the PHAR version of Pacemaker Community Edition, it is required to use the
configuration additional-vendor-dirs
directive.
{
"additional-vendor-dirs" : [ (1)
{
"vendor-dir": "vendor",
"relative": true,
"libraries": [
"techdivision/import-adapter-custom"
]
}
]
}
1 | Use the additional-vendor-dirs directive
to add additional vendor directories to the configuration |