[X] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
Not necessarily a bug but it’s crucial that in a docker or gcp cloud run deployment the .env values shouldn’t include quotation marks at all other wise it won’t work.
My local .env file had the quotation marks and when running as a docker or on gcp cloud run I was struggling to find the issue
Expected Behavior
Docker and gcp cloud run should work with the local .env
Is this a new bug?
Current Behavior
Not necessarily a bug but it’s crucial that in a docker or gcp cloud run deployment the .env values shouldn’t include quotation marks at all other wise it won’t work. My local .env file had the quotation marks and when running as a docker or on gcp cloud run I was struggling to find the issue
Expected Behavior
Docker and gcp cloud run should work with the local .env
Steps To Reproduce
Run with .env with quotation marks
Relevant log output
No response
Environment
Additional Context
No response