
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
- Console create row ui not passing ID.uni...
I'm getting an error saying the id is already used but it should be created with ID.unique() it doesn't seem to be reading the row ID field at all. I can't get ...
- [FEATURE] Better usage analytics for app...
Recently, i've gotten **73** emails from appwrite regarding excesive GBHours usage. I've almost hit the limit of 1000 and it is really hard to track down which ...
- Permissions in create_operations() Pytho...
How can I set permissions for `create_operations()`? What even is the correct way to use permissions in Python (using SDK version 13.4.1) ? In my cloud functio...
