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
- Quota not resetting
hi, im using appwrite's free tier plani hit my read limts last month and the billing cycle said it would reset on june 4th but that is today, the billing cycle ...
- Request for temporary 3 to 4 hours datab...
Hi Appwrite Team, I hope you are doing well.We are an early-stage startup currently running on Appwrite Cloud. We have unfortunately exhausted our database rea...
- Realtime Error Invalid query: Syntax err...
I was test driving Self-Hosted Appwrite for my use with Swift IOS apps as a backend while back and after successful trials, I started to move to incorporate int...