This site is hosted on a DigitalOcean droplet, which was created using Ansible (see
To re-provision the server:
# Download the required roles ansible-galaxy install -r tools/deployment/requirements.yml --force # Run the provision playbook ansible-playbook tools/deployment/provision.yml
Deployments for this site for managed with Ansible and Ansistrano. Ansible Vault is used to manage sensitive information like database passwords.
Deployments are triggered automatically when changes are pushed to GitHub, and are performed automatically via GitHub Actions on each push to the
To run a deployment manually, run
ansible-playbook tools/deployment/deploy.yml --ask-vault-pass.
The Vault password is stored in LastPass.
Generating settings files
Production settings files are generated automatically during a deployment. This is done using the opdavies.drupal_settings_files Ansible role, using variables from
tools/deployment/vars/deploy_vars.yml, and performed during Ansistrano’s
After update code build step.
Migrating data into the website
To view the status of all the migrations:
./run drush migrate:status
To run all the migrations:
./run drush migrate:import --all
To run all the migrations and update the existing migrated content:
./run drush migrate:import --all --update
Updating Drupal core
Updating Drupal core (and anything else) can be done using Composer. As this project is built using the Drupal core recommended project, all of the dependencies need to be updated:
./run composer update drupal/core-* --with-all-dependencies
Once this has completed, the updated
composer.lock file can be committed and pushed.
In order to keep the talks page in the correct order, based on when the next time a talk is being given, the
created date for the talk node is automatically updated on each save to match the date of the most future event for that talk.
The view is then sorting the talk nodes based on their