Skip to content

Commit

Permalink
Added mention of recipes:config:init:splits in config split documenta…
Browse files Browse the repository at this point in the history
…tion. (#3020)
  • Loading branch information
TravisCarden authored and ba66e77 committed Aug 29, 2018
1 parent 1373194 commit 0cb03a3
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/config-split.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ This is the simplest use case for the configuration management system.

By default, we want caching and CSS and JavaScript aggregation enabled on all of our environments. However, we would like the local environment to be an exception to this. Caching and aggregation should be disabled on local machines to expedite the development process.

To accomplish this, we will create a "local" configuration split.
To accomplish this, we will create a "local" configuration split. The command `blt recipes:config:init:splits` will create this and your other environment splits for you automatically. To create the "local" split manually, do the following:

1. `mkdir -p ../config/envs/local`
1. Navigate to `/admin/config/development/configuration/config-split/add`
Expand All @@ -79,6 +79,9 @@ To accomplish this, we will create a "local" configuration split.
weight: 0

1. `drush cr`. Doing this will allow configuration split to recognize that the local split is active. We rely on BLT to designate this split as active on local machines via a [settings.php include](https://github.com/acquia/blt/blob/9.x/settings/config.settings.php#L22).

With your "local" split ready, continue:

1. Navigate to `/admin/config/development/performance` and disable caching and aggregation.
1. `drush csex`. Because the local split is active, this will export the local split `system.performance` settings to `../config/envs/local/system.performance.yml`. It should contain the following configuration:

Expand Down

0 comments on commit 0cb03a3

Please sign in to comment.