From https://stackoverflow.com/a/68314973:
> Increasing the fastcgi_buffer_size in nginx config helped, but it
seems more like a suppression the problem, not a treatment.
> A better solution is to disable php-fpm to send logs by FastCGI. Found
it can be made by setting fastcgi.logging=0 in php.ini (by default it is
1). php docs.
> After changing it to 0, the problem goes away and nginx logs looks much
cleaner docker logs nginx:
Fixes: #463
Even though Composer v2 was being pulled from the Composer Docker image,
Composer v1 was still being used.
Because I've added the `/app/bin` path to `$PATH`, a version in
`/app/bin/composer` was being used. The simplest way that I can fix
this is re-ordering the variable so that the path is added after the
originals and the Composer version in `/usr/bin/composer` is used.
Return early within the Plausible if the user is authenticated so that
it doesn't pick up when I'm adding or editing content on the site.
Though the role is configured in the Plausible module's admin form, the
conditions in the code don't exclude it. I'll look into this further and
submit a patch upstream along with some tests.
References #350
Add the integromat webhook URL to the Ansible Vault and also to the
generated Drupal settings file that Ansible generates, and the
opdavies_blog module configuration.
References #340
This is not being done with Nginx. I've pushed the slides to Netlify and
added CNAME records in Cloudflare to serve them as subdomains as
oliverdavies.uk in the same way that I am for Rebuilding Bartik,
Rebuilding Acquia etc.
Fixes#221
Add a new `drupal-permissions` Ansible role that resets the file and
directory permissions to match the ones described in
https://www.drupal.org/node/244924.
This will later be released to Ansible Galaxy, but for now it will
remain in this repository until the required changes are made and the
appropriate documentation is added.
Fixes#191
Ensure that the configuration import is run before the database updates,
so that any new fields are created that are needed within the update
steps such as `field_type` on the talk node type.