More multisite documentation (#1049)

* Update multisite.md * Update next-steps.md
acquia · Feb 7, 2017 · 222f112 · 222f112
1 parent 0639178
commit 222f112
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git 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
@@ -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.