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
- Bug: Cloud Function On Schedule Didn't R...
Heya I have a cloud function with this cron `0 17 * * *` to run at 9AM PT every day. I have not touched this since I set it up, and it has been working fine s...
- functions
Code for function not being created in Github. Permissions are set correctly, repository is created, however no code is in the created repository. Just trying...
- Error 400: redirect_uri_mismatch
Hi team, Google OAuth was working fine with our Appwrite Cloud setup until yesterday. We did not change any configuration in Appwrite, Google Cloud, or our cod...