How to differentiate between, i.e. "stagging" and "production" instances of the database
- 0
- Databases

Hi, I've appwrite up and running on DigitalOcean and started to play around with the database creation and such. Im wondering, what's the best practice for a case when we need multiple of the exact same database for 'flavoring' purpose (stagging, prod, dev, etc)? I noticed, there's no cloning or export & import database (and/or schema) feature available on the console, so i kind of lost here.

To be honest I would use Gitpod for testing and dg for prod ( I am not a appwrite official don’t take my word for it )

so, the easiest solution would be, just runs multiple appwrite? is there an easy or simple way to export/import database schema? recreating them manually on top of managing multiple appwrite might be a bit too much.

For a one time deployment, you can use the Appwrite CLI: https://appwrite.io/docs/command-line-deployment

I definitely recommend a separate instance so that you can properly test upgrades

if i get this right, to sum it up: create separate development/stagging/etc instance of appwrite, then use appwrite cli and deploy the database to the production instance of appwrite.
Recommended threads
- import csv "Document already exists"
When I try to import a csv file to an already existing database, I keep getting "Document Already Exists" I thought that when I import and a document with the ...
- Database not found
Even though I can clearly access and update fields in my DB through the console, when my updating through the Android SDK it throws this error { "message": ...
- Cannot load nested relationships
When trying to load a nested relationship using the below query I get this error: ```Invalid query: Attribute not found in schema: *``` ```dart try { fina...
