Replies: 4 comments 2 replies
-
Thanks. Problem solved for me! |
Beta Was this translation helpful? Give feedback.
-
Yes ! I had the exact same error, until i created my own .env that appeared next to the other one : figured out that MacOs considers the file a Pages template. |
Beta Was this translation helpful? Give feedback.
-
I'm having this issue with windows |
Beta Was this translation helpful? Give feedback.
-
Please don't use finder or windows explorer for changing the .env.template if you haven't got the extention visible. |
Beta Was this translation helpful? Give feedback.
-
I've been trying to figure out why my .env file isn't working. I'm new at this, so it took some time... hope this is helpful for others out there.
First of all... I'm running macOS. It was clear that all of my errors were around missing API Keys... and lack of variables defined in the .env file.
I was editing my .env file in TextEdit. I would update my variables... change the name... and save the file. I confirmed the name change in my Finder window... but I was still getting all sorts of errors... all leading back to the .env file.
I then learned how to check the files in my directory with the:
ls -a
command to view all files (even hidden files)The command returned a list of files... including a file named ".env.template". I'm not sure why, but for some reason the name change that was showing in my finder window was not actually being recognized by the program.
Then found the command to change a file name... and it works like a charm!
mv .env.template .env
Run that line in terminal and it will force the name change.
Beta Was this translation helpful? Give feedback.
All reactions