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
- Upgrading selfhost version?
It is okay to upgrade version to higher one, of my current version is 1.7.4 to 1.8.1. Is that safe to do cause my clients already have data on that? Also is a...
- Appwrite cloud DB server error 500
Getting this error
- appwrite indexes not working (?
i have this index: ``` "indexes": [ { "key": "single-user-per-event", "type": "unique", ...