How does the update process from 1.2.1 to 1.3.x work? The documentation on appwrite.io only shows the step directly to 1.4.13. When I try to update to version 1.3.7 with the same command I get the following error.
root@Appwrite121onubuntu2004-s-1vcpu-1gb-fra1-01:~# docker run -it --rm \
TypeScript
--volume /var/run/docker.sock:/var/run/docker.sock \ --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \ --entrypoint="upgrade" \ appwrite/appwrite:1.3.7
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "upgrade": executable file not found in $PATH: unknown. ERRO[0003] error waiting for container:
Can someone please help me here
I believe that this is not the correct update command for version 1.2.1. Please can someone give me the update procedure from 1.2.1 to the current build including data migration.
For pre-1.4.x, the update command should have --entrypoint="install"
instead of
--entrypoint="upgrade"
That means I leave docker-compose up and start the upgrade with install and then perform the migration?
1.2.x -> 1.3.x -> 1.4.x
It means you execute the same command but change the upgrade
to install
You will need to take a look into what are the versions that need migration so you will need to go through them
Yes, I understood that. I'm just not sure if I should run appwrite and thus the docker-compose yaml of the old version? Or if I should first stop the already installed version with docker-compose stop and then run the install command?
First you should run installation command (in 1.4 it's upgrade instead of installation) and then you need to run the migration command. The docker compose should be updated automatically after that with newer version
When I start the upgrade command from 1.2.1 to 1.4 it overwrites all my data. I already tried that, migration was then no longer possible. That's why I'm looking for the old update and migration commands so that I can go through the steps one by one to avoid losing my data.
You should not go directly
And also from 1.3.8 to 1.4.13 you should use upgrade endpoint instead of install
Also, remember to have backups before trying
Yes, I have backups. I have already tried the upgrade a few times and had to restore the backups.
Is the documentation of the docs for the old versions still available somewhere?
In the past, you could always select the version at the top of the appwrite.io page and then the old docs were also displayed. But unfortunately I can't find that.
The migration command hasn't changed it's the update command that changed
Check the announcements channel for versions that required migration https://discord.com/channels/564160730845151244/636818236310159360
Try upgrading from 12.1 -> 1.3.0 -> 1.3.5 -> 1.3.8 (use entrypoint upgrade from here on out) -> 1.4.0 -> 1.4.2 -> 1.4.10 -> 1.4.13. Running the migration for each update
Thank you Ernest. I will try it out.
Once you have reached 1.3.8 instead of install you should use upgrade. It's not needed to go through 1.4.0 and others, you can go from 1.3.8 to latest patch
Btw, you can just upgrade to the latest patch. So it would be:
- 1.2.1
- 1.3.8
- 1.4.13
Many thanks to everyone, it worked wonderfully.
Recommended threads
- Having issues with login via CLI
``` ~/appwrite appwrite login --endpoint https://localhost/v1 --verbose ? Enter your email myvalidemai...
- Send Email Verification With REST
I am using REST to create a user on the server side after receiving form data from the client. After the account is successfully created i wanted to send the v...
- Use different email hosts for different ...
Hello, I have 2 projects and i want to be able to set up email templates in the projects. Both projects will have different email host configurations. I see ...