Just so you know, though, it won’t keep your data
docker compose down -v will delete the volumes, so there’s not a whole lot of point in keeping the original directory
You could take a backup of the current install before restoring the old one
The old one has the data I need
We've not done much with the new since all it has been showing were errors
You did the migration, right?
What version did you migrate to 1.4.1 from?
1.3.7 or 1.3.8
Not so sure
I did migration of after upgrading
You didn’t go direct, did you?
But saw an error related to _metadata
I think I saw someone else had this?
But anyway, did you go direct or step by step? So 1.3.7 to 1.3.8 to 1.4.0 to 1.4.1?
Ooops, I went direct
I have followed the instructions to restore but I get gateway timeout
It can take a few minutes for Appwrite to be available after running docker compose up -d
Oh really?
docker compose start and docker compose up -d
Which one is better?
docker compose logs appwrite seems to be good
Doesn’t start only start up already built containers? And up creates them
Ooops!
Thank you ideclon the restoration has worked
[CLOSED] Restoration is needed.
Recommended threads
- Sudden CORS Errors - Domain hasn't Chang...
I have an Appwrite project with two web apps configured, the first one has the hostname `*` and the second one I just added to test if it could fix the issue wi...
- Any way to temporarily bypass the email ...
Hey guys, any way to bypass the email verification to use the accounts again? i need to recover some projects that due to recent changes have been stopped, and ...
- Collections list not showing up when try...
I'm trying to create new relationship attribute but both one way and two way relationship is not showing up collections list to connect with my relationship att...