Rank 1: Thread
Hi, is it common that the appwrite version provided by "appwrite -v" (1.1.1) differs from the ones of the appwrite containers displayed by "docker ps | grep appwrite/appwrite" (1.3.1)?
Votes
0
Replies
17
Participants
Unknown
Messages
18
Rank 1: Thread
Hi, is it common that the appwrite version provided by "appwrite -v" (1.1.1) differs from the ones of the appwrite containers displayed by "docker ps | grep appwrite/appwrite" (1.3.1)?
Appwrite CLI version is different then Appwrite image
They have a different versions from each other
Rank 1: Thread
So when I want to upgrade to the latest version I have to start from 1.1.1 in my case?
BTW appwrite CLI is ok verison 2.x something
It's best to upgrade the CLI, yes
Rank 1: Thread
How do I do so? Nothing to do with the https://appwrite.io/docs/upgrade if I got it right(?)
That's for Appwrite on self hosted it self.
If you want to upgrade the CLI run the install process you see here again 👇
https://appwrite.io/docs/command-line#installWithNpm
Rank 1: Thread
Appwrite CLI is 2.0.2 now. So when I want to upgrade appwrite now I gotta do so from the versions shown by "docker ps | grep appwrite/appwrite"?
Didn't got this one?
Rank 1: Thread
I wanna update those to get the latest version
Rank 1: Thread
It's done by that guide isn't it? And I have to start with 1.3.2?
Yes, you'll need to this
1.3.1 -> 1.3.3 + migrate
1.3.3 -> 1.3.4 + migrate
1.3.4 -> 1.3.8 + migrate
Of course remember to backup everything first.
Rank 1: Thread
I did 1.3.1 -> 1.3.3 -> 1.3.4 -> ... -> 1.3.8 without migration at all already. Do you think thats a problem? ("You do not need to run migration when upgrading to a minor version. For example, going from 0.13.0 to 0.13.2 would not require running migration.")
you can check all the latest versions on github as well https://github.com/appwrite/sdk-for-cli/releases (keeps updated)
In this versions it's a bit different then the usual flow of Appwrite
Anyhow its best to backup & migrate now
Rank 1: Thread
I'll do so then. Thank you so much