
everything is working fine. tables are created

🥳

Should I raise a Github issue describing the condition? it needs to be fixed I guess

yes, when appwrite starts, it checks to see if the tables are there. if not, it'll create them

we may want to document the need to create the database first. I'm not sure the best way to document that @VincentGe

For external DBs right?

We can add a page under installation tbh 😛

But idk

oh duh

What is _APP_DB_ROOT_PASS
for?

I aassumed this was needed to create the Schema

when you spin up the mariadb container, it creates the database automatically.

required by the mariadb container for startup/initialization

yes! most important question lol

I seee, I'm guess it's a task we run at start up right?

It deosn't work for external instances

🤔

yes? as part of it's initialization, it creates the root account with that password, a non-root user, and the database specified

sorry, we don't run these tasks. the out-of-the-box mariadb image does this

I'm guessing if you set the root password on RDS, Appwrite should be able to create the appwrite DB right?

Although they call it "Master User" https://aws.amazon.com/premiumsupport/knowledge-center/reset-master-user-password-rds/

😑 or smthing else non-standard

[SOLVED] Unable to remotely connect to MariaDB instance

Appwrite doesn't create the database. it needs to be created beforehand

🤔 Okay so we have to explicitly create the schema I see. Thanks!
Recommended threads
- Attribute already exists in schema
I created an attribute, deleted it and now I can't create it again. It says "Failed" and "Attribute already exists in schema". ```json { "27": { "ke...
- I keep getting this error and idk why i ...
- Database error
My code: await databases.createDocument( process.env.APPWRITE_DATABASE, process.env.APPWRITE_COLLECTION_USER, data.userId, ...
