Andrew Berry

The patch itself is stored in the root of the project in a `patches` directory, not in `vendor/...`.

We ended up going with a forking model to avoid edge cases like this entirely. If you're interested, I wrote up our process over at https://www.lullabot.com/articles/patch-less-composer-workflow-drupal-using-forks.

This appears to have regressed in HEAD. In `0.3.4` I can successfully connect to hosts over an OpenVPN connection. In HEAD, while DNS resolves fine all connections time out.

You can also manually add colima in the "Firewall Options" section of Firewall in Security & Privacy in System Preferences. I am curious why it needs this in the first...

I'm on Intel, but a few months ago I was cross-compiling for ARM without issue simply by passing `--platform` as above. Now, I can't run cross-architecture at all. It looks...

Looks like `buildx` is missing entirely. It sounds like buildx is included in deb and rpm packages, but not alpine? I'm also not seeing any qemu packages installed. https://docs.docker.com/buildx/working-with-buildx/ https://github.com/docker/buildx/issues/305#issuecomment-642709911...

It does look like `docker build --platform=linux/arm64` works as expected.

At a basic level, setting `trailingSlash: true,` fixes the issue for me. As noted in the stack overflow threads, it does mean ADRs are rendered as directories, such as `http://localhost/adr/0001-record-architecture-decisions/`....

You can set it in next.config.js: https://nextjs.org/docs/api-reference/next.config.js/trailing-slash

PHP 5.3 was EOL as of August last year. The tests are failing because of short array syntax. Can we get that removed from the travis config? Or is there...