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
- Query Appwrite
Hello, I have a question regarding Queries in Appwrite. If I have a string "YYYY-MM", how can I query the $createdAt column to match this filter?
- Different appwrite IDs are getting expos...
File_URL_FORMAT= https://cloud.appwrite.io/v1/storage/buckets/[BUCKET_ID]/files/[FILE_ID]/preview?project=[PROJECT_ID] I'm trying to access files in my web app...
- Invalid document structure: missing requ...
I just pick up my code that's working a week ago, and now I got this error: ``` code: 400, type: 'document_invalid_structure', response: { message: 'Inv...