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
- 1:1 relationship doesn’t sync after re-a...
Hi, I’m trying to use a two-way one-to-one relationship. It works fine when I create a record with the relationship set, and it also works when I unset it. But ...
- Upsert with setting permissions
Hi there, I am using self-hosted appwrite v1.7.4 and trying to use the bulk update stuff that was released with 1.7.x. Unfortunally I found that there is an ser...
- Github connection error - Self Hosted Ap...
I am trying to connect my github account to deploy a project to sites, but Connect to Gtihub button is disabled. I have configured all Env variables needed for...