Rank 5: Hypervisor
Just so you know, though, it won’t keep your data
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 5: Hypervisor
Just so you know, though, it won’t keep your data
Rank 5: Hypervisor
docker compose down -v will delete the volumes, so there’s not a whole lot of point in keeping the original directory
Rank 5: Hypervisor
You could take a backup of the current install before restoring the old one
Rank 2: Process
The old one has the data I need
Rank 2: Process
We've not done much with the new since all it has been showing were errors
Rank 5: Hypervisor
You did the migration, right?
Rank 5: Hypervisor
What version did you migrate to 1.4.1 from?
Rank 2: Process
1.3.7 or 1.3.8
Rank 2: Process
Not so sure
Rank 2: Process
I did migration of after upgrading
Rank 5: Hypervisor
You didn’t go direct, did you?
Rank 2: Process
But saw an error related to _metadata
Rank 5: Hypervisor
I think I saw someone else had this?
Rank 5: Hypervisor
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?
Rank 2: Process
Ooops, I went direct
Rank 2: Process
I have followed the instructions to restore but I get gateway timeout
Rank 5: Hypervisor
It can take a few minutes for Appwrite to be available after running docker compose up -d
Rank 2: Process
Oh really?
Rank 2: Process
docker compose start and docker compose up -d
Rank 2: Process
Which one is better?
Rank 2: Process
docker compose logs appwrite seems to be good
Rank 5: Hypervisor
Doesn’t start only start up already built containers? And up creates them
Rank 2: Process
Ooops!
Rank 2: Process
Thank you ideclon the restoration has worked
[CLOSED] Restoration is needed.