Fixes issue where .env file is invalid

[adamlc]

This fixes #60 where the .env file is created without quotes

[jbrooksuk]

Most of these settings should never need to be double-quoted, but if it works then it's only going to prevent issues further down the line 👍

[adamlc]

Ill be honest I didn't think all of them would need to be, but I guess it won't hurt though 😄

[djdefi]

Interesting find.

Dotenv values containing spaces must be surrounded by quotes.

Out of curiosity, which attribute were you using a space in?

[jbrooksuk]

Usually it's MAIL_NAME that causes an issue.

[adamlc]

Yeah it was just MAIL_NAME actually. I guess thats probably the only one that will need double quotes. I'm not sure if theres a better way of doing this in the entrypoint script?

[jbrooksuk]

This is probably the simplest place.

[adamlc]

Shall I modify the PR to only change the MAIL_NAME?

[jbrooksuk]

It's possible that MAIL_PASSWORD could have a space.

[adamlc]

Well does it hurt leaving them all double quoted?

[jbrooksuk]

Not that I know of.

[mattallty]

It hurts: see #151