Managed DataBase Env?

Hi. Where can I find the Managed Database Env because I want to use Managed MariaDB.

TL;DR

The user is asking about setting up Appwrite on Kubernetes and using managed databases. They want to know if Appwrite Functions are being used and if there will be any sharing of insights. They express the desire to not manage the database on a local server due to concerns about redundancy, high availability, and backups. They mention they are currently using Appwrite with Kubernetes and it is working well. They ask if the support team can explain what they mean by managed databases and offer alternative methods. The support team mentions that currently, Appwrite only allows connecting to MariaDB, but they plan to support other database backends in the future. The user

And what to change to Change to Managed DB?

Hey

Can you elaborate a bit about this?

Yeah. If I want to Change from local Database to Managed Db for Appwrite, What env variables to Change?

For now you can run AppWrite with MariaDB only so if you want to have managed one you'll need to update the following variables _APP_DB_HOST - Your managedDB host. _APP_DB_PORT - Your managedDB port _APP_DB_SCHEMA - Through what scheme, if exporting and importing leave it on appwrite _APP_DB_USER - Your managedDB Don't run on root _APP_DB_PASS - User passwwod _APP_DB_ROOT_PASS - Root password

The quick way would be to dump all the current database data and import it to a remote one

P.S, You can this vars inside either the docker-compse.yml or the .env in the path /root/appwrite or your appwrite location (if you created a custom one)

It is better to edit the values inside the .env file

Hmm so. So Matej once mentioned that: As of right now, Appwrite only allows you to connect to MariaDB, but we plan to support any database backend, such as MySQL, Postgres or MongoDB.

Gladly, Appwrite API is built in a way that database layer does not make much of a difference, what matters, is the API structure that you consume. It might feel a bit strange for someone with backend experience to see extra layer on top of database that Appwrite uses, but it's there to create consistency no matter what database you will choose in future.