To avoid any confusion
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
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.backup
home
|__ appwrite
|__ docker-compose.yml
|__ appwrite <== get rid of this
|__ appwrite
this is the folder after removing
perfect
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
--volume /var/run/docker.sock:/var/run/docker.sock \
--volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
--entrypoint="install" \
appwrite/appwrite:1.3.8
just to make sure i should use the above command
step by step until 1.3.8
yes exactly
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
oh God. am now at 1.2.0 whats the next patch?
look at the releases
I've managed to reach 1.3.8 thanks
[SOLVED] Migration error when upgrading from 0.15.3 to 1.3.8
Recommended threads
- Can't really use the S3 storage device
hi, I've linked my local MinIO Instance (it's just for testing, not for prod.) to my appwrite instance, when i'm uploading a file it's getting uploaded to the S...
- Next.js SSR Site Times Out on First Visi...
Hey everyone, I'm running a Next.js SSR site on a self-hosted Appwrite server (v1.9.0), and I've noticed a strange behavior that I'm hoping someone can help me...
- Quota not resetting
hi, im using appwrite's free tier plani hit my read limts last month and the billing cycle said it would reset on june 4th but that is today, the billing cycle ...