Ted B

> We're not sure why the instance metadata endpoint failed in our case, but we'll look in to it. Amazon [does note](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html#instancedata-throttling) that they recommended consumption of the instance meta...

I've successfully redeployed with `v1.2.9`

I've tested this and it works well just by setting this in the config/vars: ```yaml postgresql_data_dir: "/data/pgsql/{{ postgresql_version }}/data" ``` Much easier to move the data to another mounted volume

I guess this is no longer being maintained

I hit the same issue. This is the only image without `arm64`. https://hub.docker.com/r/easyengine/php/tags

Instead of the (it seems default) plain formatter try `--format=sublime` like this: node_modules/.bin/esvalidate --format=sublime index.js It gives a more readable output such as: [esvalidate src\getDocument.js] 16,46: Unexpected token =>