The best way to write the migration script for database schema for long term maintenacy
- 0
- Self Hosted
- Tools
- Databases
I want to keep track of what have changed in the database schema, collection schema. everytime, there is changes, we create new migration script for example. just like asp.net migration script. how to archeive this. any plan appwrite creating migration script like this in the future.
You can do the same thing as those migration scripts but using the server SDK
any good pratical sample to share
This asp.net example 😜
🤣 anyone done in appwrite yet
Haven't heard of any
usually, and pratically, we use console to manage right
Ya but that's not scripting the migrations...the equivalent thing in asp.net would be to use SQL management studio
would you mind suggesting me, what if we have few devs, we have different local dev instance of appwrite, how can we keep everyone sync in the same page, of database schema.
backup/restore is option, but won't be easy to keep it synced
if appwrite has ability to keep track of what has been changed ( such as collection schema, or even data). then able to generate the chaanges into script and able to share to other to just run it . this would be life saver.
The appwrite CLI has a json file, but it's only for clean deployments since it deletes attributes and recreates them.
yes. right.
Recommended threads
- Edit ID of an existing collection
Hi there. Is it possible to edit an ID of an existing collection? Right now it looks impossible from AppWrite cloud at least.
- Migrate from cloud to localhost
Hello everyone. I need to migrate my test project from cloud to localhost, however it seems that this is possible only if a self-hosted appwrite instance it's h...
- Seed db
hello there... is this correct way to seed appwrite