Drupal is a registered trademark of Dries Buytaert
Views Bootstrap 5.5.2 Minor update available for module views_bootstrap (5.5.2). oEmbed Providers 3.0.0 Major update available for module oembed_providers (3.0.0). Byte (theme) 1.0.3 Minor update available for theme byte_theme (1.0.3). Token Content Access 3.1.3 Minor update available for module tca (3.1.3). Emulsify 7.2.1 Minor update available for theme emulsify (7.2.1). Opensolr Search 4.1.0 Minor update available for module opensolr_search (4.1.0). AG-UI 1.0.2 Minor update available for module agui (1.0.2). FileGate 1.5.0 Minor update available for module file_gate (1.5.0). oEmbed Providers 2.2.4 Module oembed_providers updated after 7 months of inactivity (2.2.4). Provus Mega Menu Module provus_mega_menu crossed 1,000 active installs.

This recipe installs and configures the Config Split module to manage environment-specific Drupal configurations for development, staging, and production. It provides a baseline setup with pre-defined splits that can be activated by adding custom logic to your settings.php file.

A Drupal recipe that installs Config Split and creates an opinionated baseline of three environment-specific split entities (dev, staging, prod) for managing configuration across different deployment environments.

What This Recipe Provides

This recipe automates the setup of Configuration Split with pre-configured split entities for common deployment workflows:

Dev split – Enables admin tools, debugging modules, and development-focused configuration
Staging split – Contains pre-production testing configuration overrides
Prod split – Carries production-ready performance and security-related configuration

How It Works

The recipe creates three split entities with `status: false` by default. You activate the appropriate split for each environment by adding override logic in your `settings.php`:

```php
// Example: Activate the correct split based on environment
$split = getenv('DEPLOY_NAME') ?: 'dev';
$config['config_split.config_split.' . $split]['status'] = TRUE;

Split folder contents are stored under config/split/{dev,staging,prod}/ and are read by Config Split at runtime (they are not imported by this recipe).

Installation

composer require drupal/config_split_recipe

drush recipe config_split_recipe

drush cr

Post-Apply Steps

  1. Add settings.php logic to activate the correct split for your environment
  2. Populate your split folders with environment-specific configuration
  3. Test config import/export workflows across all environments
  4. Adjust split blacklists/graylists to match your project needs

Requirements

  • Drupal 10.3 or Drupal 11
  • Config Split 2.x

Important Notes

  • This is a baseline, not a fully generic Config Split toolkit
  • Split activation requires custom settings.php logic tailored to your hosting platform
  • The shipped split definitions may need adjustment for your specific project
  • Split entities are created disabled; you control when they activate

Recommended companion project:

Recipes Manager makes recipes much easier to work with in real projects because it brings recipe discovery and management into the Drupal UI. If your team wants a smoother editorial and admin workflow for applying and reviewing recipes, this is the easiest way to get it.

Activity

Total releases
1
First release
Jun 2026
Latest release
1 month ago
Releases (12 mo)
1 ▲ from 0
Maintenance
Active

Releases

Version Type Release date
1.0.x-dev Dev Jun 16, 2026