Ansible and Pantheon » History » Version 1
Jon Goldberg, 12/21/2021 02:04 AM
| 1 | 1 | Jon Goldberg | # Ansible and Pantheon |
|---|---|---|---|
| 2 | |||
| 3 | Ansible *can* be used to successfully create local dev sites for Pantheon: |
||
| 4 | * Install Terminus somewhere in the global path (e.g. /usr/local/bin) |
||
| 5 | * Create a machine token in Pantheon, add it to `pass` at the root of the client directory (e.g. `reamp/pantheonmachinetoken`) (only necessary once per live site) |
||
| 6 | * There are overrides, a "pantheon" group, and a "Pantheon Site Code" field in the Website List. Check an existing Pantheon site. |
||
| 7 | * You also need to override the Civi db name on all sites to indicate they're all the same database. |
||
| 8 | * DB sync strategy on the Website List live site entry should be "Pantheon". |
||
| 9 | * Add both your own SSH public key and the key of the "run as" user to your Pantheon account. |
||
| 10 | * Manually SSH into the git server as "run as" user to add to known_hosts (for git) |
||
| 11 | * Probably running without tags is fine, but this is known to work: `ansible-playbook main-playbook.yml -l mysite.local --tags site-upa,site-mysql,site-main,site-db-sync,site-dns,site-permissions` |