Folder structure of configuration files

Edited 1 year 6 months ago

Base path: ./

├── ./config
│   ├── ./config/boutiquein
│   ├── ./config/budweisercom
│   ├── ./config/coronacom
│   ├── ./config/davinci
│   │   └── ./config/davinci/dx8
│   ├── ./config/default
│   │   └── ./config/default/language
│   │       ├── ./config/default/language/en
│   │       └── ./config/default/language/pt-br
│   ├── ./config/envs
│   │   ├── ./config/envs/dev
│   │   ├── ./config/envs/local
│   │   ├── ./config/envs/prod
│   │   └── ./config/envs/stage
│   ├── ./config/features
│   │   ├── ./config/features/colors
│   │   ├── ./config/features/migrate
│   │   └── ./config/features/packages
│   ├── ./config/profiles
│   │   ├── ./config/profiles/abi_sitestudio
│   │   │   └── ./config/profiles/abi_sitestudio/language
│   │   │       ├── ./config/profiles/abi_sitestudio/language/en
│   │   │       └── ./config/profiles/abi_sitestudio/language/pt-br
│   │   └── ./config/profiles/abi_standard
│   └── ./config/tapit
│       └── ./config/tapit/language
│           └── ./config/tapit/language/en

./config/default => Configurations that will be applied to all sites regardless of the installed profile

./config/envs => Configurations that will be applied in specific environments (Configuration split)

./config/profiles => Configurations that will be applied based on the installed profile

others => Configurations for specific sites (manual import required)

Configuration files (Config Ignore)

.config/default/config_ignore.settings.yml => Configurations that should be ignored when importing/exporting site settings.
./config/default/config_split.config_split.ignored.yml => settings that should be ignored when importing/exporting site settings. Cohesion settings are being ignored in this file
What should I put in the Config Ignore?

When you want to keep a certain configuration in the environment without changing it during the import.

Let's say that you do would like the system.site configuration (which contains the site name, slogan, email, etc.) to remain untouched, on your live site, no matter what the configuration in the config folder is.

https://www.drupal.org/project/config_ignore
Configuration files (Config Split)

./config/default/config_split.config_split.abi_sitestudio.yml => Configuration split for sites that was created based on ABInbev Site Studio profile
./config/default/config_split.config_split.abi_standard.yml => Configuration split for sites that was created based on ABInbev Standard profile
./config/default/config_split.config_split.davinci.yml => Specific configuration for DaVinci as a Components Catalog
./config/default/config_split.config_split.dev.yml => Specific configuration for dev environment
./config/default/config_split.config_split.ignored.yml => This config-split setting deploys configuration only in database not in the config''s folders.
./config/default/config_split.config_split.local.yml => Specific configuration for local environment
./config/default/config_split.config_split.prod.yml => Specific configuration for prod environment
./config/default/config_split.config_split.stage.yml => Specific configuration for stage environment
When should I use Config Split?

In the simplest scenario, we want to enable a few extra modules on development environments (Devel, Kint, Stage File Proxy, Views UI, etc.), but not have these modules enabled on production.

Component Menu

Folder structure of configuration files

Configuration files (Config Ignore)