Site Studio
Drupal config vs Site Studio packages
Site Studio leverages Drupal configuration entities for all templates, components and styles that are created using the low-code interface. As such the package export and import process utilises the Drupal core configuration management workflow at it's core, however, it is important to note that the two are not interchangeable and Site Studio's packaging system should be used due to the additional functionality it provides as highlighted below.
When using Site Studio package management alongside Drupal core configuration management the Config Ignore and Config Split modules should also be configured.
Import and export feature comparison:
| Drupal config | Site Studio packages |
|---|---|
| Exports configuration entities | Exports configuration entities |
| Imports configuration entities | Export file entity dependencies and metadata |
| Ignores missing file entity dependencies | Imports configuration entities |
| Performs Drupal validation | Imports file entity dependencies |
| Performs Drupal validation | |
| Performs Site Studio validation | |
| Performs Site Studio data integrity checks (optional in v6.8+) | |
| Handles Site Studio entity rebuilds |
Acquia recommends that you install the Site Studio Configuration Management module after you use Site Studio with the Drupal configuration management system. This module provides best-practice settings for config_ignore and config_split modules to ensure that Site Studio configuration is handled correctly during deployment synchronizations.
Without proper configuration management rules, deployment configuration synchronizations delete critical Site Studio settings from the database, such as API keys, Agency keys, and API server URLs. This issue causes Site Studio rebuilds to fail, triggers resource exhaustion loops, and results in complete site downtime.
Config Ignore
Prevents the system from overwriting specified configuration items during import.
Config Split
Enables environment-specific configuration. For example, this module manages different settings for development, staging, and production environments.
Site Studio Configuration Management
Provides recommended config_ignore and config_split settings specifically for Site Studio.
Add the following to your config_ignore settings at a minimum to protect Site Studio configuration during deployments:
Site Studiocohesion.settingsRefer to the settings that Site Studio Configuration Management module provides for a complete list of recommended ignore rules.
| Exports configuration entities |
| Imports configuration entities | Export file entity dependencies and metadata |
| Ignores missing file entity dependencies | Imports configuration entities |
| Performs Drupal validation | Imports file entity dependencies |
| Performs Drupal validation |
| Performs Site Studio validation |
| Performs Site Studio data integrity checks (optional in v6.8+) |
| Handles Site Studio entity rebuilds |
Acquia recommends that you install the Site Studio Configuration Management module after you use Site Studio with the Drupal configuration management system. This module provides best-practice settings for config_ignore and config_split modules to ensure that Site Studio configuration is handled correctly during deployment synchronizations.
Without proper configuration management rules, deployment configuration synchronizations delete critical Site Studio settings from the database, such as API keys, Agency keys, and API server URLs. This issue causes Site Studio rebuilds to fail, triggers resource exhaustion loops, and results in complete site downtime.
Config Ignore
Prevents the system from overwriting specified configuration items during import.
Config Split
Enables environment-specific configuration. For example, this module manages different settings for development, staging, and production environments.
Site Studio Configuration Management
Provides recommended config_ignore and config_split settings specifically for Site Studio.
Add the following to your config_ignore settings at a minimum to protect Site Studio configuration during deployments:
cohesion.settingsRefer to the settings that Site Studio Configuration Management module provides for a complete list of recommended ignore rules.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.