Download the PHP package yoanm/composer-config-manager without Composer
On this page you can find all versions of the php package yoanm/composer-config-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yoanm/composer-config-manager
More information about yoanm/composer-config-manager
Files in yoanm/composer-config-manager
Package composer-config-manager
Short Description command line to manage composer configuration file
License MIT
Informations about the package composer-config-manager
composerConfigManager
Command to manage composer configuration file
- Install
- How to
- Managed properties
- Full composer configuration
- Contributing
Install
Add the following in your .bashrc
file :
How to
just type the following
In case you launch the command from the repository directory, you can simply use
- Type
composercm list
to list all available command - Type
composercm help COMMAND_NAME
orcomposercm COMMAND_NAME -h
to display help for a specific command
See below for more information regarding command line options
-
composercm update
command will take the current composer.json file and will applied given valuesCreate
- A
--template
option is available, given values will be applied to the template - Values are appended in a default order
Update
- A
--template
option is available, see below how templates are managed - Key order are kept from old configuration file. New one are appended in a default order
Templates
-
Multiple template could be provided. Update workflow is the following
-
1 - Templates between them If more than one template is given,
- the first first one is updated with values from the second one
- resulting configuration is updated with third template
...
- resulting configuration is updated with X template
- 2 - Resulting configuration with existing one
- For update command only, in case at least a template was given
- 3 - Resulting configuration with command line values
- Could by skipped if only templates are used
-
Key order
- By default key order as the one defined in composer documentation website
-
It's possible to use the
--template
option to define key order of final configuration For instance, defined a template file namekey_order.json
with following content :Then use the following command :
Resulting file will have keys ordered like in
key_order.json
file. All keys could be added inkey_order.json
, in case no value is given for a key, key will not appear in final file.In case you also want to provide a template with default value, use the following:
Managed properties
Following properties could be defined with option from command line :
- Package name
- Package type
- License
- Version
- Description
- Keywords Many allowed
- Author Many allowed
- Provided packages Many allowed
- Suggested packages Many allowed
- Support Many allowed
- PSR-0 / PSR-4 Autoload Many allowed
- PSR-0 / PSR-4 Autoload dev Many allowed
- Required packages Many allowed
- Required dev packages Many allowed
- Scripts
All others properties could ever be defined in templates and will be managed in a default way (could produce unexpected merge for complex nested values)
Full composer configuration
Contributing
See contributing note
All versions of composer-config-manager with dependencies
symfony/console Version ~3.0
symfony/dependency-injection Version ^3.2
symfony/serializer Version ^3.2
symfony/filesystem Version ^3.2
symfony/config Version ^3.2
symfony/finder Version ^3.2