Configuration management enhances the stability, reliability, and speed of deploying features to production websites in Drupal. It allows tracking and exporting configurations, treating the entire site as a feature, and integrates with version control for smooth deployment across environments. However, it is not suitable for managing sensitive configurations or certain default settings, which can be excluded as needed.

1. Developing with
Configuration
Management
Ryan Szrama, DrupalCamp Asheville 2014

2. Why do configuration management?
Configuration management improves:
1. The stability of a production website.
2. The reliability of feature deployment to a
production website.
3. The speed of feature deployment to a
production website.

3. Manage configuration in code.
● Baseline for dependable feature development
and deployment in Drupal.
● Commit it to your repository so it can be moved
between environments; typically more useful
than sharing features between sites.
● Do it manually, use Features, or use
Configuration Management.

4. What’s Configuration Management?
The Configuration Management module treats
your entire site as a Feature.
● Backport of Drupal 8 “CMI” work.
● Lets you track configurations, export them
from the active store (database) to the data
store (file system), and synchronize the
active store with the data store.

13. What isn’t it good for?
1. Overriding default configurations.
2. Managing menu items.
3. Managing environment specific configuration
or sensitive configuration (e.g. API keys).
a. Fortunately, you can exclude any configuration you
want through the settings form.

15. How does it work on Platform.sh?

16. How does it work on Platform.sh?

17. How does it work on Platform.sh?

18. How does it work on Platform.sh?

19. How does it work on Platform.sh?

20. How it works on Platform.sh:
1. Track a collection of configurations.
2. Write them to the data store using a writable
files directory.
3. Export them and copy the tracked.inc and
configuration .inc files to /config in Git.
4. Commit and push to rebuild the environment.
5. Merge commits upstream
6. Synchronize from sites/default/config.

21. What’s next?
Check out the results of the Configuration
Management Initiative in Drupal 8:
https://austin2014.drupal.org/session/introducing-drupal-8-
configuration-system