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.

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

More multisite documentation #1049

Merged
merged 2 commits into from
Feb 7, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 6 additions & 0 deletions readme/multisite.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,10 @@ Ensure that your new project has `$settings['install_profile']` set, or Drupal c

At this point you should have a functional multisite codebase that can be installed on Acquia Cloud.

## Drush aliases

The default Drush site aliases provided by [Acquia Cloud](https://docs.acquia.com/acquia-cloud/drush/aliases) and [Club](https://github.com/acquia/club#usage) are not currently multisite-aware. They will connect to the first ("default") site / database on the subscription by default. You will need to create your own Drush aliases for each site.

It's recommended to copy the aliases file provided by Acquia Cloud or Club to create a separate aliases file for each site. Simply modify the `uri` and `parent` keys for the aliases within each file to match the correct database / site.

TODO: Add instructions for integration with BLT development workflows and DrupalVM.
4 changes: 4 additions & 0 deletions readme/next-steps.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,3 +56,7 @@ Other commonly used commands:

# update BLT
composer update acquia/blt --with-dependencies

## Drush aliases

It's recommended to install Drush aliases in your repository that all developers can use to access your remote sites. If you are using Acquia Cloud, follow the instructions on [Acquia Cloud](https://docs.acquia.com/acquia-cloud/drush/aliases) or use [Club](https://github.com/acquia/club#usage) to download your aliases and place them in the `drush/site-aliases` directory.