To avoid any confusion
[SOLVED] Migration error when upgrading from 0.15.3 to 1.3.8
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
so the original appwrite folder is the first one. and i get rid of the children?
get rid of the appwrite folders inside the first one
so for example
Rank 3: Container
drwxr-xr-x 2 root root 4096 Aug 8 20:13 .drwx------ 7 root root 4096 Dec 9 2022 ..-rw-r--r-- 1 root root 3103 Aug 7 21:35 .env-rw-r--r-- 1 root root 3151 Aug 7 08:52 .env.1691398363.backup-rw-r--r-- 1 root root 3064 Aug 7 21:35 .env.1691444128.backup-rw-r--r-- 1 root root 17996 Aug 7 21:35 docker-compose.yml-rw-r--r-- 1 root root 17996 Aug 7 08:52 docker-compose.yml.1691398363.backup-rw-r--r-- 1 root root 18733 Aug 7 21:35 docker-compose.yml.1691444128.backuphome
|__ appwrite
|__ docker-compose.yml
|__ appwrite <== get rid of this
|__ appwrite
Rank 3: Container
this is the folder after removing
perfect
Rank 3: Container
what about the .env backups
now go to the parent directory with cd .. and run the upgrade commands there
make sure you run migrate commands too!
that's completely fine
you don't need to worry about those
Rank 3: Container
--volume /var/run/docker.sock:/var/run/docker.sock \ --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \ --entrypoint="install" \ appwrite/appwrite:1.3.8Rank 3: Container
just to make sure i should use the above command
Rank 3: Container
step by step until 1.3.8
yes exactly
Rank 3: Container
1.1.0 then 1.1.1 then 1.1.2 then 1.2.0 then 1.2.1 then 1.3.0 then 1.3.2 then 1.3.3 then 1.3.4 then 1.3.5 then 1.3.6 then 1.3.7 then 1.3.8
no
Rank 3: Container
oh God. am now at 1.2.0 whats the next patch?
look at the releases
Rank 3: Container
I've managed to reach 1.3.8 thanks
[SOLVED] Migration error when upgrading from 0.15.3 to 1.3.8