From what I'm seeing Appwrite has an env var for MariaDB called _APP_DB_ROOT_PASS
, but there are other variables for a custom DB user and password, so the thing is if is really needed for appwrite to have access to both the root user and an aditional user specified with the _APP_DB_PASS
variable
Appwrite itself never uses that variable as can be seen in the docker-compose.yml
file
...
- _APP_DB_HOST
- _APP_DB_PORT
- _APP_DB_SCHEMA
- _APP_DB_USER
- _APP_DB_PASS
...
The only reason is to set the MariaDB root password in case it needed
And, it's best to set it upfront
So I should leave that password in blank?
No, just put a very strong password
Obviously from the database side I will put a very strong password. The thing is that if I should specify or not that password in the env var. From what I understood, it's not needed specifying the root password, right?
In that case, you can get a warning that you'll need to allow an empty password.
Recommended threads
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- Can't login or deploy functions in Appwr...
Hello, since i updatet to the appwrite cli 6.1.0 i can't login or deploy functions with the cli. When i call the command: "appwrite get account --verbose" i ge...
- Create admin user?
I'm not really sure how this is supposed to work, I installed Appwrite through docker-compose and set it up. When I launched the app and went into it, I created...