[Bug]: .env file is not written correctly when variable value contains a space

[victorlap]

Description

I was trying to deploy a laravel application, and for the APP_NAME variable I have a string with a space.

Apparently coolify doesn't handle this well, since it doesn't escape this in the .env file that is written. vlucas/phpdotenv crashes when it sees an unescaped value with whitespaces.

Minimal Reproduction (if possible, example repository)

Create new coolify project using example repo: https://github.com/victorlap/coolify-env-repro
Set build to Dockerfile
Add environment variable with space in value
Try to deploy

Exception or Error

I see the following error:

26.57 Failed to parse dotenv file. Encountered unexpected whitespace at [My String].

I tried quoting the value myself, but then the quotes get escaped:

28.97 Failed to parse dotenv file. Encountered unexpected whitespace at [\"My String\"].

Version

v4.0.0-beta.294

[victorlap]

I found a workaround by adding the quotes myself and selecting 'is literal'.

I do think that it would be nice if this works out of the box though.

[iFlyinq]

I found a workaround by adding the quotes myself and selecting 'is literal'.

I do think that it would be nice if this works out of the box though.

Encountering this one as well, but the trick you suggest doesn't seem to fix it.

[JuanxCursed]

I found a workaround by adding the quotes myself and selecting 'is literal'.

I do think that it would be nice if this works out of the box though.

That made the trick to me

[ZackBz]

I found a workaround by adding the quotes myself and selecting 'is literal'.
I do think that it would be nice if this works out of the box though.

Encountering this one as well, but the trick you suggest doesn't seem to fix it.

I just tried this as i was facing the same issue in my app and it did work. Make sure to enter the variable in double quotes and check 'is literal' as @victorlap suggested. Also don't forget to save, and redeploy/restart.

[JuanxCursed]

It started happening again on version v4.0.0-beta.325

[2024-Sep-04 01:16:49.633208] failed to read /artifacts/t8s0g0wkc0kko0oswwcookog/.env: line 6: unexpected character "/" in variable name

The weird part is that there isn't a / character on this variable (both on generated .env at the server or my own env lines)

[JuanxCursed]

I've deleted all my env variables, but I'm still getting the "same error"

GTM_ID=
NUXT_PUBLIC_METAPIXEL_DEFAULT_ID=

I noticed that the error changed when I changed the resource name as well, Leads / Anamnese to Leads

[2024-Sep-04 01:36:45.721585] failed to read /artifacts/x0c080sowcwsws4wwowso4gk/.env: line 6: key cannot contain a space

[AndreVarandas]

In my case (laravel app) it was picking up the Project Name as the APP_NAME.
Overriding it in the environment variables didn't work. I had to rename the project and it worked right away.

[Sillyvan]

In my case (laravel app) it was picking up the Project Name as the APP_NAME. Overriding it in the environment variables didn't work. I had to rename the project and it worked right away.

Just ran into the same issue!

[saullo]

In my case (laravel app) it was picking up the Project Name as the APP_NAME. Overriding it in the environment variables didn't work. I had to rename the project and it worked right away.

I lost a lot of time at work because of this same problem...

[ktufekcic]

I've been encountering a very different problem but possibly related. When Coolify adds the .env file, it also adds some of it's own env vars, most relevant here being COOLIFY_APP_NAME, which corresponds to the name you gave to your resource, and if this has spaces, it will always include them in the .env file, and the only fix (that I could come up with) is to just not have spaces in any resource names

[andrasbacsai]

I've been encountering a very different problem but possibly related. When Coolify adds the .env file, it also adds some of it's own env vars, most relevant here being COOLIFY_APP_NAME, which corresponds to the name you gave to your resource, and if this has spaces, it will always include them in the .env file, and the only fix (that I could come up with) is to just not have spaces in any resource names

This will be fixed in the upcoming version.