-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
PL-46: D7 domain examples #13
Closed
Closed
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
- Use the `fs-demo` domain for all sites and use different subdomains. - Create a config split for the Domain Access solr index so that the site name can be different. See `field_settings.site_name.configuration.site_name`. - Create a config split for the Domain Access solr settings so that the hash can be different. Otherwise the document keys are the same and overwrite each other. See `site_hash`.
This allows config overrides for Domain Access to take into affect and avoids overwriting of Solr documents because of identical IDs.
I'll re-open this when I have it in a ready state. Like #11, I'm getting the installation error:
|
The Domain Access check to see if `drush si` is being used wasn't working. This approach uses a pre-install settings.php file and a post-install file with the Domain Access include.
…en installing all sites. The `build.drupal.settings_dest` is set when the library is loaded, but it needs to change based on the site, so we pass those parameters in when we call `drupal-prepare-settings`.
I've updated the build task to use a pre-install and post-install settings.php. It looks like Domain Access tries to detect if Drush is running, but it wasn't working and this seems to get the job done. |
damontgomery
changed the title
PL-46: D7 domain access examples
PL-46: D7 domain examples
Jan 4, 2019
It's not really `Domain Access`, but `Domain`.
Closed
This has been superceded by more recent work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JIRA Ticket(s)
Description
Add Drupal 7 site with Domain example.
This includes work from #12 since that deals with some of the same files.
This is a rework of #11 with changes including those in #12.
Testing instructions
phing build install-all
from inside the VMRelevant Screenshots/gifs:
Pull Request Guidelines