Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention recipes:config:init:splits in Config Split documentation #3020

Merged
merged 2 commits into from
Aug 29, 2018
Merged

Mention recipes:config:init:splits in Config Split documentation #3020

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
68754e9
Added mention of recipes:config:init:splits in config split documenta…
TravisCarden Aug 20, 2018
5515cc9
Merge branch '9.x' into config-split-recipe
ba66e77 Aug 29, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/config-split.md
View file
Open in desktop
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