Skip to content

Clarify configuration scope #1614

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

Merged
Parent: Update importing_assets_from_bundle.md
merged 1 commit into from
May 12, 2022
Merged

Clarify configuration scope #1614

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/guide/multisite/multisite_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,11 +94,11 @@ The available scopes are:
3. SiteAccess group
4. `default`

The scopes are applied in the order above. This means that `global` overrides all other scopes.
`global` overrides all other scopes.
If `global` is not defined, the configuration then tries to match a SiteAccess, and then a SiteAccess group.
Finally, if no other scope is matched, `default` is applied.

In short: if you want a match that always applies, regardless of SiteAccesses use `global`.
In short: if you want a match that always applies, regardless of SiteAccesses, use `global`.
To define a fallback, use `default`.

``` yaml
Expand Down