opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 3 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Move all files to old/drupal/

Browse source
This commit is contained in:
Oliver Davies 2025-10-02 07:57:25 +01:00
parent 8203e983d5
commit 7d76bf2968
468 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

67
README.md
View file

@ -1,67 +0,0 @@
# oliverdavies.uk
## Hosting
This site is hosted on a DigitalOcean droplet, which was created using [Ansible][] (see `tools/deployment/digitalocean.yml`).
[Ansible]: https://www.ansible.com
## Provisioning
To re-provision the server:
```bash
# Download the required roles
ansible-galaxy install -r tools/deployment/requirements.yml --force
# Run the provision playbook
ansible-playbook tools/deployment/provision.yml
```
### Deploying
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 `production` branch.
To run a deployment manually, run `ansible-playbook tools/deployment/deploy.yml --ask-vault-pass`.
The Vault password is stored in LastPass.
[Ansistrano]: https://ansistrano.com
#### Generating settings files
Production settings files are generated automatically during a deployment. This is done using the [opdavies.drupal_settings_files][drupal_settings_files] Ansible role, using variables from `tools/deployment/vars/deploy_vars.yml`, and performed during Ansistrano’s `After update code` build step.
[drupal_settings_files]: https://galaxy.ansible.com/opdavies/drupal_settings_files
## Local development
### 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.
## Talks ordering
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 `created` date.