Skip to main content
added 645 characters in body
Source Link
leymannx
  • 18.8k
  • 6
  • 72
  • 126

Install Config Ignore and configure it to ignore those config objects from which you think they are going to be changed in production.

Ever experienced that your site's configuration was overridden, by the configuration on the filesystem, when doing a drush cim?

Not anymore!

This module is a tool to let you keep the configuration you want, in place.

Lets say that you do would like the system.site configuration (which contains that sites name, slogan, email, etc) to remain untouched, on your live site, no matter what the configuration, in the config folder, says.

Or maybe you are getting tired of having the devel.settings changed every time you import configuration?

Then this module is what you are looking for.

Install Config Ignore and configure it to ignore those config objects from which you think they are going to be changed in production.

Install Config Ignore and configure it to ignore those config objects from which you think they are going to be changed in production.

Ever experienced that your site's configuration was overridden, by the configuration on the filesystem, when doing a drush cim?

Not anymore!

This module is a tool to let you keep the configuration you want, in place.

Lets say that you do would like the system.site configuration (which contains that sites name, slogan, email, etc) to remain untouched, on your live site, no matter what the configuration, in the config folder, says.

Or maybe you are getting tired of having the devel.settings changed every time you import configuration?

Then this module is what you are looking for.

Source Link
leymannx
  • 18.8k
  • 6
  • 72
  • 126

Install Config Ignore and configure it to ignore those config objects from which you think they are going to be changed in production.