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
- All My Project is Gone
Hello everyone, please help. Why have all my projects suddenly disappeared? I received a warning via email about one of my projects being paused. When I clicked...
- Courtesy limit reset for non-profit migr...
Hi Team! I'm the architect for a 501(c)(3) non-profit project (Aaria's Blue Elephant) and we just hit our Free plan Database Read limit (currently at 164%). Th...
- Does 1.9.0 Self Hosted have MongoDB Atla...
I have been playing with the new 1.9.0 update and I am really excited for the MongoDB support. I wanted to ask though if at the current time Appwrite supports b...