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
- Updating GitHub App access throws error
Steps to reproduce - 1. Have some private repos allowed on the install access 2. New Site/Func > Connect GitHub > see the side card saying `Missing a repo` > cl...
- New Build not visible on Domain
I pushed some new code to my Appwrite Site and the build succeeded and is shown as active. Yet, I can only see the new version of the site on Appwrite's provide...
- DNS bug
Hello, we found bug at the Appwrite Cloud Domains, when changing **only ** the Comment of CNAME, we get error DNS record already exists. Some DNS types do not ...