
I used the one click setup on digital ocean and when I loaded into the console and navigated to the appwrite folder I noticed there is no env file present and only the docker file.
Do I need to point appwrite at an env file if I upload one? If so how do I make sure it's using the env for configuration.
If there's any documentation I may have missed please point me in the right direction!

I should also mention I set the global variables in the project settings in the appwrite console and it seems like none of them applied after running docker compose up -d

Those global variables have nothing to do with your .env file. They are for functions so that you don't need to define the same variable across multiple functions

In Unix systems, files and folders that start with a dot are hidden. You can see all files and folders (including hidden) by using ls -a

Didn't even think about hidden files, not super well versed with unix systems. Thanks!

[SOLVED]Digital ocean one click setup, env file creation help.
Recommended threads
- Functions not work on Server only Localh...
Hi, I successfully upgraded from 1.4 to 1.7, but I'm having a problem. The functions no longer work with the settings I had. I assume some changes were made. It...
- Console Login after upgrade
Hi, running a small instance self hosted, upgraded from 1.6.0 to 1.74 this morning before spotting the migration guide... When trying to login to the console n...
- Appwrite functions can't connect to data...
I'm trying to create a function that queries my database, but all database operations timeout from within the function, even though CLI access works perfectly. ...
