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
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....
- User ID case sensitivity
I see that through REST (and SDK as well), getting a user is not case sensitive. And even though documentation does not clearly state that it is, the wording "V...