
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
- Hello guys
First of all thank you very much for so good application. I have self-hosted AppWrite instance on my VPS. It is working on http protocol 90 and https 543. These...
- Which is the best self hosting plan out ...
I am loving appwrite cloud from day 1 . But due to recent pricing changes which only allows a single project for base price would prove very costly for my remai...
- Function not creating documents
So Im having this issue where no error is thrown at all but my function isn't able to create documents inside my database. ```typescript import { Client, Databa...
