This page has moved to Adobe Experience League and will be redirected soon.
.magento.env.yaml changes not shown in env.php after deploy
.magento.env.yaml changes not shown in env.php after deploy
NOTE
If you have this problem upgrade to ece-tools 2002.1.5 to fix it. 2002.1.5 has functionality to reset the opcache on each deployment so there is never a need to change the setting opcache.enable_cli=1. If you don't want to upgrade, then you would have to do the workaround steps as described below in the solution.
This article provides a solution for the issue where changes in .magento.env.yaml file are not reflected in app/etc/env.php after deployment.
Affected products and versions
Issue
Changes made in the .magento.env.yaml file do not affect the app/etc/env.php generated.
Steps to reproduce:
Change any value in .magento.env.yaml and push to the server, where it should define the configuration (and deployment settings) for the currently checked-out environment. For steps, see Environment Variables > Deploy Variables in our developer documentation.
Expected result:
Changes made in the .magento.env.yaml file affect the app/etc/env.php generated.
Actual result:
The changes have no effect on the app/etc/env.php variables after deployment.
Cause
The issue could be caused by the incorrect value of the opcache.enable_cli parameter in the php.ini file.
Solution
- Check that the system is configured according to Adobe Commerce Performance Best Practices > Software recommendations.
- Check if
opcache.enable_cli directive in php.ini is set to 0 by executing: php -i | grep opcache.enable_cli
- If the output looks like
opcache.enable_cli=1 , edit the php.ini file in the project root directory and change opcache.enable_cli=1 to opcache.enable_cli=0
- Redeploy the project.