Magento – app:config:dump locks everything in configuration

configurationdeploymentmagento2.2

I am using pipeline deployment. As suggested in Magento 2.2 documentation, to use pipeline deployment process use below code:

app:config:dump

and add config.php to source control. But when i execute app:config:dump it locks everything in system configuration.
Even not able to update store email addresses.

Is there any way to dump only required settings that will be used to generate static content on build system?

I am confused whether to use pipeline deployment or not.
I am using Magento 2.2 CE Open Source version.

Any one has implemented pipeline deployment and any suggestion for me.

Thanks in advance.

Best Answer

You need to delete all data from app > etc > config.php except modules array.

After run below command
setup:upgrade
setup:di:compile
setup:static-content:deploy -f
cache:flush.

All your system configuration are unlocked and you can change the value of it.

Working build system

Based of issue 10041 for RC version I figure that we need to remove env.php file if exist.

Second issue 11372 throwing error:

Fatal error: Uncaught Error: Call to a member function getPackage() on null in /srv/magento2/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 217

Error: Call to a member function getPackage() on null in /srv/magento2/vendor/magento/module-deploy/Package/Processor/PostProcessor/CssUrls.php on line 217

This is caused by previously genereated cache on var/view_preprocessed, to fix this we need to remove cache:

rm -rf pub/static/* 
rm -rf var/view_preprocessed/pub

Full steps to deploy static content on build system:

Run container with mounted our magento

docker run -it -v $HOME/www/magento2:/srv/magento2 bmxmale/magento2-php:2.2-cli bash

Remove cache

rm -rf pub/static/* 
rm -rf var/view_preprocessed/pub

Deploy static content for backend

php bin/magento setup:static-content:deploy -f en_US -t Magento/backend

Deploy static content for frontend

php bin/magento setup:static-content:deploy -f da_DK -t OurTheme/default

Magento – GIT deployment and what files are required in production environment

I suggest you read some articles about processes already used by some, such as :

and then appropriate those to your needs.

You may install Magento on production, staging and development environments the same way, then you just deploy versioned files (not ignored from .gitignore file). Optimized gitignore files can be found on GitHub, from the official Magento repository to other sources.