Deploying with Ansible » History » Version 2
Jon Goldberg, 11/09/2020 07:37 PM
| 1 | 2 | Jon Goldberg | {{last_updated_at}} by {{last_updated_by}} |
|---|---|---|---|
| 2 | |||
| 3 | 1 | Jon Goldberg | # Deploying with Ansible |
| 4 | |||
| 5 | ## Ansible with multisite CiviCRM |
||
| 6 | Our configuration supports CiviCRM multisite where there are multiple CMSes and a single CiviCRM database. To deploy in this configuration: |
||
| 7 | * Add the first site to the [https://crm.megaphonetech.com/website-list] and install normally. |
||
| 8 | * Once installation on site 1 is complete, install the [Multisite Permissioning](https://civicrm.org/extensions/multisite-permissioning) extension and create the database records for site 2. |
||
| 9 | * Add the second site to the [https://crm.megaphonetech.com/website-list] and install **normally**, ignoring multisite. Note that you'll probably need to override the DB User, CMS DB Name and CRM DB Name to prevent collisions with site 1. |
||
| 10 | * Once the site is up and running, open the entry in the website list, go to *Overrides*, and make the following changes: |
||
| 11 | * Change the "Multisite Domain ID" to `2`. |
||
| 12 | * Change the "CRM DB Name" to match that of site 1. Leave the "CMS DB Name" and "DB User" different from site 1. |
||
| 13 | * Re-run Ansible. |
||
| 14 | * Drop the CRM database created for site 2. |
||
| 15 | * Repeat as necessary for other sites. |