Environment-specific config with Configuration Split

In this talk, we'll explore how the Configuration Split module can be used to have certain Drupal configuration items active in specific environments (as opposed to always being active).

For example, it is a best practice for performance and security to disable modules used solely for development in a website's production environment while leaving them enabled in local and cloud development environments. We can easily implement this best practice using the Configuration Split module.

To get the most out of this talk, you should already be familiar with importing and exporting Drupal configuration (whether via the admin UI or using a command line tool such as Drush or Drupal Console) in Drupal 8 or 9.