Managing configuration across environments and sites with Configuration Split
Drupal's configuration management system is an important tool for safely working with the configuration of our sites. With it, we can develop, share, test, and deploy configuration consistently in all the different environments that are part of modern development workflows.
But what if we don't want that configuration to be consistent everywhere? Local development environments have different needs than production servers. Multi-site installs or other sites sharing a code base might share a lot of configuration, but aren't exactly the same.
In this session, we'll learn about the Configuration Split module and how it lets us make specific changes to configuration in different situations. We'll get our bearings by setting up a split for a basic development environment. Then we'll see how to use splits to share configuration in a multi-site install. Finally, we'll go over some important tips for keeping those splits manageable.
But what if we don't want that configuration to be consistent everywhere? Local development environments have different needs than production servers. Multi-site installs or other sites sharing a code base might share a lot of configuration, but aren't exactly the same.
In this session, we'll learn about the Configuration Split module and how it lets us make specific changes to configuration in different situations. We'll get our bearings by setting up a split for a basic development environment. Then we'll see how to use splits to share configuration in a multi-site install. Finally, we'll go over some important tips for keeping those splits manageable.