Download the PHP package zendframework/zend-component-installer without Composer
On this page you can find all versions of the php package zendframework/zend-component-installer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zendframework/zend-component-installer
More information about zendframework/zend-component-installer
Files in zendframework/zend-component-installer
Package zend-component-installer
Short Description Composer plugin for injecting modules and configuration providers into application configuration
License BSD-3-Clause
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 zend-component-installer
Component Installer for Zend Framework 3 and Expressive Applications
Repository abandoned 2019-12-31
This repository has moved to laminas/laminas-component-installer.
This repository contains the Composer plugin class Zend\ComponentInstaller\ComponentInstaller,
which provides Composer event hooks for the events:
- post-package-install
- post-package-uninstall
Via Composer global install
To install the utility for use with all projects you use:
Per project installation
To install the utility for use with a specific project already managed by composer:
Writing packages that utilize the installer
Packages can opt-in to the workflow from zend-component-installer by defining
one or more of the following keys under the extra.zf configuration in their
composer.json file:
-
A component is for use specifically with zend-mvc + zend-modulemanager; a
Moduleclass must be present in the namespace associated with it. The setting indicates a low-level component that should be injected to the top of the modules list of one of:config/application.config.phpconfig/modules.config.phpconfig/development.config.php
-
A module is for use specifically with zend-mvc + zend-modulemanager; a
Moduleclass must be present in the namespace associated with it. The setting indicates a userland or third-party module that should be injected to the bottom of the modules list of one of:config/application.config.phpconfig/modules.config.phpconfig/development.config.php
- A config-provider is for use with applications that utilize
expressive-config-manager
or zend-config-aggregator
(which may or may not be Expressive applications). The class listed must be an
invokable that returns an array of configuration, and will be injected at the
top of:
config/config.php
Whitelisting packages to install automatically
At the project level, you can mark packages that expose configuration providers
and modules that you want to automatically inject via the component-whitelist
key:
This configuration must be made at the root package level (the package consuming configuration providing packages).
All versions of zend-component-installer with dependencies
composer-plugin-api Version ^1.0