
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
- Looking for Partner
I'm looking for partner for long-term collaborating. Of course, I'll pay for you. If you are interested, Please DM me.
- Issue - Migration From Cloud > Self Host...
Hi team, Iām trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in āarchive modeā due to th...
- Why "Youāve reached the limit for your G...
Why did Appwrite send me this alert when the usage reached 10605%? Is it too late? Why not when reached 100% usage? And I can not pay for more usage described ...
