Yii Config

This Composer plugin provides assembling of configurations distributed with composer packages. It is implementing a plugin system which allows to provide the configuration needed to use a package directly when installing it to make it run out-of-the-box. The package becomes a plugin holding both the code and its default configuration.

Requirements

• PHP 8.0 or higher.
• Composer 2.0 or higher.

Installation

How it works?

The package consist of two parts: Composer plugin and config loader.

After composer updates its autoload file, and that happens after dump-autoload, require, update or remove, Composer plugin:

• Scans installed packages for config-plugin extra option in their composer.json.
• Writes a merge plan into config/.merge-plan.php. It includes configuration from each package composer.json.

In the application entry point, usually index.php, we create an instance of config loader and require a configuration we need:

The web in the above is a config group. The config loader obtains it runtime according to the merge plan. The configuration consists of three layers that are loaded as follows:

• Vendor configurations from each vendor/package-name. These provide default values.
• Root package configurations from config. These may override vendor configurations.
• Environment specific configurations from config. These may override root and vendor configurations.

Please note that same named keys are not allowed within a configuration layer.

When calling the get() method, if the configuration group does not exist, an \ErrorException will be thrown. If you are not sure that the configuration group exists, then use the has() method:

Config groups

Each config group represents a set of configs that is merged into a single array. It is defined per package in each package composer.json:

In the above example the mapping keys are config group names and the values are configuration files and references to other config groups. The file paths are relative to the source-directory, which by default is the path where composer.json is located.

Markers

• ? - marks optional files. Absence of files not marked with this marker will cause exception.

  It's okay if params-local.php will not be found, but it's not okay if params.php will be absent.

• * - marks wildcard path. It means zero or more matches by wildcard mask.

  It will collect all web.php in any sub-folders of src/Modules/ in config folder. However, if the configuration folder is packaged as part of the PHAR archive, the configuration files will not be uploaded. In this case, you must explicitly specify each configuration file.

• $ - reference to another config by its group name.

  The config groups params-console and params-web will both contain the config values from params.php and params-local.php additional to their own configuration values.

Define your configs like the following:

A special variable $params is read from config (by default, group is named params).

Using custom group for $params

By default, $params variable is read from params group. You can customize the group name via constructor of Config:

You can pass null as $params group name. In this case $params will empty array.

Using sub-configs

In order to access a sub-config, use the following in your config:

Options

A number of options is available both for Composer plugin and a config loader. Composer options are specified in composer.json:

source-directory

The source-directory option specifies where to read the configs from for a package the option is specified for. It is available for all packages, including the root package, which is typically an application. The value is a path relative to where the composer.json file is located. The default value is an empty string.

If you change the source directory for the root package, don't forget to adjust configs path when creating an instance of Config. Usually that is index.php:

vendor-override-layer

The vendor-override-layer option adds a sublayer to the vendor, which allocates packages that will override the vendor's default configurations. This sublayer is located between the vendor and application layers.

This can be useful if you need to redefine default configurations even before the application layer. To do this, you need to create your own package with configurations meant to override the default ones:

And in the root file composer.json of your application, specify this package in the vendor-override-layer option:

In the same way, several packages can be added to this sublayer:

You can use wildcard pattern if there are too many packages:

For more information about the wildcard syntax, see the yiisoft/strings.

Please note that in this sublayer keys with the same names are not allowed similar to other layers.

merge-plan-file

This option allows you to override path to merge plan file. It is .merge-plan.php by default. To change it, set the value:

This can be useful when developing. Don't forget to set same path in Config constructor when changing this option.

build-merge-plan

The build-merge-plan option allows you to disable creation/updating of the config/.merge-plan.php. Enabled by default, to disable it, set the value to false:

This can be useful when developing. If the config package is a dependency of your package, and you do not need to create a merge plan file when developing your package. For example, this is implemented in yiisoft/yii-runner.

package-types

The package-types option define package types for process by composer plugin. By default, it is "library" and "composer-plugin". You can override default value by own types:

Environments

The plugin supports creating additional environments added to the base configuration. This allows you to create multiple configurations for the application such as production and development.

Note that environments are supported on application level only and are not read from configurations of packages.

The environments are specified in the composer.json file of your application:

Configuration defines the merge process. One of the environments from config-plugin-environments is merged with the main configuration defined by config-plugin. In given example, in the dev environment we use $web configuration from the main environment.

This configuration has the following structure:

To choose an environment to be used you must specify its name when creating an instance of Config:

If defined in an environment, params will be merged with params from the main configuration, and could be used as $params in all configurations.

Configuration in a PHP file

You can define configuration in a PHP file. To do it, specify a PHP file path in the extra section of the composer.json:

Configurations are specified in the same way, only in PHP format:

If you specify the file path, the remaining sections (config-plugin-*) in composer.json will be ignored and configurations will be read from the PHP file specified. The path is relative to where the composer.json file is located.

Configuration modifiers

Recursive merge of arrays

By default, recursive merging of arrays in configuration files is not performed. If you want to recursively merge arrays in a certain group of configs, such as params, you must pass RecursiveMerge modifier with specified group names to the Config constructor:

If you want to recursively merge arrays to a certain depth, use the RecursiveMerge::groupsWithDepth() method:

Note: References to another configs use recursive modifier of root group.

Reverse merge of arrays

Result of reverse merge is being ordered descending by data source. It is useful for merging module config with base config where more specific config (i.e. module's) has more priority. One of such cases is merging events.

To enable reverse merge pass ReverseMerge modifier with specified group names to the Config constructor:

Note: References to another configs use reverse modifier of root group.

Remove elements from vendor package configuration

Sometimes it is necessary to remove some elements of vendor packages configuration. To do this, pass RemoveFromVendor modifier to the Config constructor.

Remove specified key paths:

Remove specified configuration groups:

Combine modifiers

Config supports simultaneous use of several modifiers:

Commands

yii-config-copy

The plugin adds extra yii-config-copy command to Composer. It copies the package config files from the vendor to the config directory of the root package:

Copies all config files of the yiisoft/view package:

Copies the specified config files of the yiisoft/view package:

In order to avoid conflicts with file names, a prefix is added to the names of the copied files: yiisoft-view-params.php, yiisoft-view-web.php.

yii-config-rebuild

The yii-config-rebuild command updates merge plan file. This command may be used if you have added files or directories to the application configuration file structure and these were not specified in composer.json of the root package. In this case you need to add to the information about new files to composer.json of the root package by executing the command:

Testing

Unit testing

The package is tested with PHPUnit. To run tests:

Mutation testing

The package tests are checked with Infection mutation framework with Infection Static Analysis Plugin. To run it:

Static analysis

The code is statically analyzed with Psalm. To run static analysis:

License

The config package is free software. It is released under the terms of the BSD License. Please see LICENSE for more information.

Maintained by Yii Software.

Credits

The plugin is heavily inspired by Composer config plugin originally created by HiQDev (https://hiqdev.com/) in 2016 and then adopted by Yii.

Support the project

Follow updates