config.php generated automatically with ECE-Tools v2002.0.5 and later
With the Ece-Tools v2002.0.5 and later, the
config.php file is generated automatically during the build phase if it doesn’t already exist.
Modify affected settings in config.php only, not in Magento Admin
All settings in the
config.php file are locked in Magento Admin; the corresponding Admin sections are grayed out and cannot be accessed.
To change the settings, affected by Configuration Management, on a particular environment, edit the
config.php file on such environment.
Read it on DevDocs: Update configurations.
Sensitive values are stored in env.php, not in config.php
The sensitive application data (like payment processor passwords, API keys, DB access credentials, etc.) are stored not in the
config.php but the
env.php file (on a server) as environment variables.
To access or modify the sensitive data, SSH to your server and edit the
/app/etc/env.php file. You can also manually add sensitive environment variables using the Project Web Interface, the CLI, or in the Magento Admin.
Read it on DevDocs: Configuration management for store settings
Knowledge Base articles on Configuration Management
Configuration Management on DevDocs
- Configuration management for 2.1.X and the example in the Magento Commerce (Cloud) Guide
- Configuration management for 2.2.X and the example in the Magento Commerce (Cloud) Guide
- Upgrade from 2.0.X or 2.1.X section of the Upgrade Magento Commerce (Cloud) topic
- Pipeline Deployment in the Magento Configuration Guide — For Magento Commerce (Cloud), you do not need to follow the instructions in this guide. The content is strictly for reference. We already provide the build server, integration environments, and more with Cloud.