This repository was archived by the owner on Mar 5, 2025. It is now read-only.
Support for multisite deploys #1092
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
danepowell
commented
Feb 14, 2017
| dir: ${docroot} | ||
| uri: ${multisite.name} | ||
| uri: default |
There was a problem hiding this comment.
This change should have no effect for single-site projects. Multisite projects should pass either a unique cloud alias or override drush.uri, for instance via example.multisite.yml.
This was referenced Feb 16, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes two significant changes:
multisite.namevariable is currently overloaded. Sometimes it is used as an array, and sometimes as a single-value string. The only reason it works at all is because the output is identical in both cases for single-install sites. But for multisite projects, we need to decouple this in some places.