Hi, I have a self hosted instance running on version 1.4.2. I want to upgrade to the latest version. In the 1.4.2 changelog it was mentioned to run the migrate command but after that i can't see a mention of it anywhere else. As a suggestion, it would be better if the upgrade command took care of migration when needed as well.
Generally migration is required when upgrading to a minor version such as 1.3.8 to 1.4.x . I think there were some internal changes that required migration from 1.40 to 1.4.2. You can upgrade to the latest patch without migration since it's still 1.4.x
i've seen in <#564160731327758347> someone mentioning a migration is necesary in between, doesn't remember where, so just wanted to ask the staff.
You can run migration if you want to be really sure, though I don't think it's necessary
There's not issue in running it if it's not needed?
Yes
However, it's important to backup just in case
If changelogs dont explicitly say run migration then dont.
Ensure you backup, upgrade and check if everything works. If so, dont run migration, if something seems off, run it.
I upgraded from 1.4.5 to 1.4.13 and ran migration n my functions stopped executing. Not saying migration had anything to do with it but thats what happened. I am currently in the process of migrating data to a new server so be careful and can't stress this enough, take a back up
https://discord.com/channels/564160730845151244/1186081774216941668
I do have an automatic backup system setup since one update broke everything even in production.
It just doesn't give me the confidence to use appwrite when even upgrading can cause downtime. Taking backup and restoring when things go wrong is just too much downtime
I use to avoid that a parallel instance
First I migrate to the temp parallel instance, then I switch there and after upgrading everything I switch back to the original instance
I know it's not the best approach but 🤷♂️
that is still downtime
When you migrate using migrations feature there's not any downtime
Well, if you have lots of requests then yes, there's a small downtime between switches
But sincerely, I don't think that's bad at all. You can do it in less active hours. In my case I have 99.98% uptime
Since you mentioned migration, can you take a look
https://discord.com/channels/564160730845151244/1186936605806710815
Recommended threads
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- Can't login or deploy functions in Appwr...
Hello, since i updatet to the appwrite cli 6.1.0 i can't login or deploy functions with the cli. When i call the command: "appwrite get account --verbose" i ge...
- Create admin user?
I'm not really sure how this is supposed to work, I installed Appwrite through docker-compose and set it up. When I launched the app and went into it, I created...