From 222f1122e490000476e44015b7526862da9e80fa Mon Sep 17 00:00:00 2001 From: Dane Powell Date: Tue, 7 Feb 2017 12:24:36 -0800 Subject: [PATCH] More multisite documentation (#1049) * Update multisite.md * Update next-steps.md --- readme/multisite.md | 6 ++++++ readme/next-steps.md | 4 ++++ 2 files changed, 10 insertions(+) diff --git a/readme/multisite.md b/readme/multisite.md index 3130db802..8ff53fa72 100644 --- a/readme/multisite.md +++ b/readme/multisite.md @@ -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. diff --git a/readme/next-steps.md b/readme/next-steps.md index cf058190a..ef190831d 100644 --- a/readme/next-steps.md +++ b/readme/next-steps.md @@ -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.