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.
Summary
The user wants to know how to differentiate between staging and production instances of the database. The suggested solution is to create separate instances and use the Appwrite CLI to deploy the database to the production instance. It is recommended to have a separate instance for proper testing. For a one-time deployment, the Appwrite CLI can be used. It is also suggested to use Gitpod for testing and dg for production. There is no built-in database cloning or export/import feature in the Appwrite console.
ski
Rank 2: Process
Apr 29, 2023, 02:55
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 )
NgekNgok
@everyone
Apr 29, 2023, 02:59
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.
I definitely recommend a separate instance so that you can properly test upgrades
NgekNgok
@everyone
Apr 29, 2023, 09:28
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.