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
- Weird permission failure
when creating an account I use following methods: ``` Future<void> register(String email, String password, String username) async { final user = await accoun...
- Relation Question
How do I create a relation from table y to an others x.$id. in my example I have a users table where I use Appwrites unique User IDs and I want other tables fo...
- Unknown attribute type: varchar / text
Since the `string` type is deprecated I tried using `varchar` and `text` in some newer tables, but when running `appwrite pull tables && appwrite types ./src/li...