Initialization fails with ill-fitting NotFound custom error when .env file is not encoded as UTF8

[Nimelrian]

When the .env file is saved with something other than a UTF-8 encoding, the initialization returns a NotFound custom error, which gives users the wrong lead when debugging.

Another error should be returned instead (wrong encoding).

[svanas]

Confirmed. This causes the Getting Started guide to fail on Windows, because...

echo DATABASE_URL=postgres://username:password@localhost/diesel_demo > .env

...generates a UTF-16 encoded file (not a UTF-8 encoded file).

[guitartsword]

Same here!