The Magical Configuration Management Unicorn
summary
Claim: Drupal 8 configuration management is useful but not magical — real sites need patterns and contributed tools to handle exceptions. Example: six separate show sites share a base config but keep environment-specific settings out using config_split and a dev-only directory; panels pages that must be identical get exported as panels pages as config. Deployments use automated imports with drush config-import --partial to avoid deleting editor-created config, and initial site provisioning uses configuration_installer to install from the same config set.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker intro
- 1:51Why configuration management matters
- 5:09Drupal 8 vs Drupal 7 explained
- 7:58Content vs configuration theory
- 10:35Gray areas in config management
- 13:49Environment differences and tools
- 15:59Key configuration modules overview
- 17:25Config split deep dive
- 19:12Dev environment configuration splits
- 21:27Config installer module use case
- 23:15Automating configuration imports
- 26:56Real-world challenges and solutions
- 27:40Q&A on panels pages and config splits
- 30:11Q&A on export strategies and performance
- 32:02Q&A on single-item exports and features
- 34:52Q&A on tools and alternatives
- 36:37Q&A on multi-site configuration
- 38:09Closing and resources
related talks
50mConfiguration management in Drupal 8 for beginners
37mExtend Configuration Management with "Config Split" and "Config Ignore" module
46mDrupal’s Scariest Things
32mThe Necessity of Configuration and System Management Tools
40mConfiguration Management Initiative 2.0 updates
13mConfig Management for Programmers: How to Set Up Virtual Machines the Easy Way
22mConfiguration Management Systems on the Desktop
50mExiting Vacuum: Integrating Configuration Management into your Ecosystem