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
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...
- User Filter/Sorting/Analytics
Currently the dashboard for users is very limited. I would like to have an option to sort by column and also to filter by column, to for example find users that...
- function subdomain ssl certs
The generated subdomain isn't getting a valid ssl cert, I was wondering if appwrite automatically generates one or uses a wildcard for *.functions.domain.com? ...