Need to update app through 54 updates in short period of time

[ChristopherMag]

The wekan app became unsuitable for us to use after upstream version 7.97, cloudron version 4.75.0. When this happened about 9 months ago we restored from backup, disabled updates, and made a clone with updates enabled so that we could check functionality periodically to see when it would be safe to upgrade.

The app recently has started making changes to address the issues introduced after 7.97 and I am now beginning to prepare for eventually upgrading as it looks like that might be an option for us.

The latest cloudron app version is 4.129.0 so there are 54 versions we need to update through to get from the version we are on to the latest version.

I need to test the entire upgrade process and confirm everything works properly after the upgrade and then prepare for doing the process again during a weekend when no one is in the office.

For the first test I have cloned again and started doing the updates with no backups through the web interface but this process is going to take too long even for testing purposes and definitely too long when doing it for the production cutover.

I have tried to use the cloudron cli to automate this but the update command does not appear to be able to function in the same way clicking update on the web interface does. At minimum it appears to need to be executed from a clone of the repo of the app your updating and it seems like it wants the repo to be the version to which your updating.

If I am understanding that right then I would have to clone https://git.cloudron.io/packages/wekan-ap and then via git change the repo version to be one ahead of the version the app is on and then do the update command, roll the git repo forward and repeat. I believe I might also need to use the --image parameter and keep updating the identifier of the image to match the version I am trying to upgrade to https://hub.docker.com/r/cloudron/io.wekan.cloudronapp/tags.

There may be some nuances I have wrong but it does seem like whatever the options those are going to be very difficult to execute.

I may be just missing something, what is the best way to accomplish this?

PS, there may be an app specific backup and restore method and I am working on trying to see if I can make that work though it is not clear whether there is an option for that that preserves everything and works when there has been a gap of many versions between the two.

[jdaviescoates]

@ChristopherMag I've only skim read your post but the "standard" hack in this scenario is to change the update schedule to hourly and then wait for for them to go through all the updates one by one each hour.

[ChristopherMag]

@jdaviescoates Makes sense.

Given the quantity of updates and the necessity of them all being completed in shorter time span than the fastest automatic update schedule option, hourly, I don't think it would be a solution in this case.

[james]

Similar topic to https://forum.cloudron.io/topic/15674/bulk-wordpress-updates and also answered there.

[ChristopherMag]

@james That looks perfect, I will try to implement that solution.

[ChristopherMag]

@james I have implemented what you recommended but it doesn't appear to do the update if it hasn't detected an update is needed.

If I leave it alone it will do one update and then stop, if I got to the updates screen it doesn't list any pending updates, if I click check for updates and it shows an update is needed and then wait about a minute, it will automatically install the update but if I then wait 5+ minutes it won't install another update until I go back and click check for updates.

Do I need to do something else to get this to work?

PS, this also appears to be making backups even though I have turned automatic backups off for this app so I would still need a way to stop those as well as I am trying to accomplish the same thing as click the update button with the skip backup option checked in the GUI but through some more automatic means.

[joseph]

@ChristopherMag if you are comfortable with CLI, then you can cloudron update --app wekan.domain.com --appstore-id io.wekan.cloudronapp@4.125.0 --no-backup .

• Do this on a cloned app
• Of course, upstream wekan is not testing jumping versions like this randomly. So, anything can happen.
• Use the changelog to map package version to the wekan upstream version .

[ChristopherMag]

@joseph I didn't realize that I could use --appstore-id and then not have to deal with the image and manifest issues.

I will give that a try, even if I don't jump versions, if this works I can make something that will step through each of the versions incrementally until it reaches the current version automatically. Thank you!