
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
- Collection Permission issue
I am facing issue in my Pro account. "Add" button is disabled while adding permission in DB collection settings.
- Opened my website after long time and Ba...
I built a website around a year back and and used appwrite for making the backend. At that time the website was working fine but now when i open it the images a...
- Unable to create push providers - FCM or...
Currently unable to create a push provider for FCM or APNS.... https://github.com/appwrite/console/issues/2045 When uploading a file... FCM = Valid file retu...
