One of our developers kinda messed up the project, is there a way I'm missing on how to avoid this for future scenarios? In the self-hosted version we could do backups in cheeky ways, but the only way I can see of making a backup from the cloud is to make a migration to another account or self hosted instance 😅
Other than backing up the schema (with appwrite init, which is only really good for deploying a new instance of a project, because you lose any data in the database), no, there aren’t really currently any options.
So I truly will use the migration feature as a backup <:appwritemagician:946072299172409414>
Although a backup/restore process is in the concept stages currently
I guess so?
I found this repo, but I can’t speak to whether it’ll be any use https://github.com/react-declarative/appwrite-backup-tool
If your issue has been solved, you can mark this post as closed by adding “[SOLVED]” to the beginning of the title
Recommended threads
- 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...
- I'm experiencing a critical bug on Appwr...
Hey <@870607367597850624> team / support 👋 I'm experiencing a critical bug on Appwrite Cloud that's blocking my production Flutter app. I've already filed GitH...