Customizing An Environment
Further information on customizing or extending an environment is forthcoming. For now, this section is limited to very simple and somewhat common customizations.
To configure your project with a non-default PHP version, add the following to the project’s
.env file and run
warden env up to re-create the affected containers:
The versions of MariaDB, Elasticsearch, Varnish, Redis, NodeJS and Composer may also be similarly configured using variables in the
Start of some environments could be skipped by using variables in
Docker Specific Customizations
To override default docker settings, add a custom configuration file in your project root
This file will be merged with the default environment configuration.
One example for a use case is the setup of multiple domains.
PHP Specific Customizations
To override default php settings, follow the docker customization above and include your custom
In this case the
warden-env.yml should look like this:
Now add the referenced
.warden/php/zz-config.ini file with your wanted changes.
For example you could change the error reporting value:
error_reporting=(E_ALL ^ E_DEPRECATED)
The config file will be merged with the default
01-php.ini resp. override the values
included there. The default values are the following:
date.timezone = UTC
max_execution_time = 3600
max_input_vars = 10000
memory_limit = 2G
display_errors = On
post_max_size = 25M
session.auto_start = Off
upload_max_filesize = 25M
Nginx Specific Customizations
To override the default nginx configuration of your project, add a new file
.warden/warden-env.yml to your project root with the following content:
There you can specify a custom Nginx configuration which will be included following the
.conf files within the
Magento 1 Specific Customizations
If you use a
modman structure, initialize the environment in your project path.
.modman folder and the corresponding
.basedir file will be recognized and set up automatically.
Magento 2 Specific Customizations
The following variables can be added to the project’s
.env file to enable additional database containers for use with the Magento 2 (Commerce Only) split-database solution.
Start of some Magento 2 specific environments could be skipped by using variables in