Skip to main content


Configuration files

The project is able to work with different configurations for different environments. Each environment is defined by a set of configuration files and only the current environment is loaded into the container.

Let's say we want to work with a development environment and a production environment. We will have two sets of configuration files, one for each environment.

Let's call development as dev and production as prod. You need to create a folder called config in your project root at the same level of the vendor directory.

Inside these folders create files called "config-dev.php", "config-test.php" where dev, test, live, etc are your configuration sets.

Your folder will look like to:

<project root>
+-- config
+ .env
+ config-dev.php
+ config-dev.env
+ config-prod.php
+ config-prod.env
+-- vendor
+-- composer.json

The .env file

The *.env is a file that contains the environment variables that will be loaded into the container. The format is:


; This is a comment
; By default all variables are parsed as string.
; If you want to parse as boolean, integer or float, you need to use the type casting
; By default, all properties are parsed as string. You can parse as bool, int or float as this example:

PARAM1=!bool true
PARAM2=!int 20
PARAM3=!float 3.14

The file named .env will be loaded to ALL ENVIRONMENTS.

The .php file

The *.php needs to return an associative with the configuration values. It can return:

  • A single value
  • A closure - It will process the value only when it is requested
  • A dependency injection definition

return [
'property1' => 'string',
'property2' => true,
'property3' => function () {
return 'xxxxxx';
'propertyWithArgs' => function ($p1, $p2) {
return 'xxxxxx';
SumAreas::class => DI::bind(SumAreas::class)

Advanced configuration

It is possible instead of a single file, you can have a folder with multiple files. The files will be loaded in alphabetical order.

Each folder inside the config directory will be the name of the environment. The example below will have two environments: dev and prod.

The file names inside the folder doesn't matter and don't need to be same in the other environments. The only thing that matters is the extension. It can be only .env or .php.

<project root>
+-- config
| |
| +-- dev
| | |
| | + .env
| | + config.php
| | + config.env
| +-- prod
| |
| + .env
| + config.php
| + config.env
+-- vendor
+-- composer.json

This option is useful when you have a lot of configuration files, and you want to split them into multiple files.

You can combine both folder and standalone files. In that case the individual files will take precedence over folder files.

Inheritance between environments

One environment can inherit from another. This means that the environment that inherits will have all the variables of the inherited environment and can override them if the names matches.

That's very important because you can have a common configuration for all environments and override only the variables that are different.

Load Priority

If you have multiple files and the same variable is defined in more than one file, the system will override the value with the value defined by the last file loaded with the same variable.

The load order is:

  • config-<ENV>.php
  • config-<ENV>.env
  • <ENV>/*.php
  • <ENV>/*.env
  • .env

Open source ByJG