Solved Unable to upgrade Wallabag

[jk]

Hi,
I read in the app updates section for Wallabag that in order to upgrade the app, one needs to create a new app with the latest version and then export and import.

I have tried to do that, but I'm stuck at the export step. First, the app was OOM-killed. Then I increased it's memory to 8GB and restarted the app. That didn't help.

I found out that in /etc/apache2/sites-enabled/wallabag.conf the PHP memory limit is hardcoded to 64MB. That is not enough to export all ~17500 entries into a single file.

Putting the app into recovery mode still does not allow me to change that file and try again.

Do you have any suggestions on how to solve this?

Thank you!

[girish]

@jk If you have the CLI tool, you can do cloudron debug --app wallabag.domain.com. Then, you can edit the apache file and then run /app/code/start.sh.

[jk]

Thank you. Some busy days ahead, but I'll try this soon and report back.

[jk]

It took a while, but finally the migration succeeded.

None of the original approaches worked. In the end, I had to manually create a DB backup from the host (SSH to cloudron host, docker exect postgresql, pg_dump from there), modify it and import it into the db of the new app.

That was quite an arduous process, even though the DB schema had not changed between the two versions.

So for future reference, I think this is the "streamlined" version:

• Download the file /app/data/data/site-credentials-secret-key.txt from the old app, and upload it to the new app.
• Open the web terminal for both apps, and do the following for each:
  • Click the postgres button
  • Put "echo" before the psql command and run it. This will give the full login command for the app.
  • Copy the command
• Login to the cloudron host, and get a root shell.
• Execute this command: docker exec -it postgres /bin/bash
• Log in to the database of the new app and clear all tables
• Exit this database
• Run the following command: PGPASSWORD=<old_app_password> pg_dump -h postgresql -p 5432 -U <old_app_username> -a <old_app_schema> > /tmp/backup.sql
• Run the following command: psql -d <new_app_schema> < /tmp/backup.sql

After that, you should be able to log in to the new app, and have everything as it was.

[jk]

Even though I am usually very happy with Cloudron and its support, I was less impressed with it this time.

In the end, it looks like this only needed a direct data migration (db and /app/data/), which should be fairly easy given one has full control over the platform.

So I don't understand why the app packagers have chosen not to do this in this case, and thereby make it such an arduous process. Especially given the care that is usually taken to make upgrades smooth.

[girish]

@jk Thanks for the write up! Indeed, the migration is a bit rough because Wallabag had made a 2.3.8 release back in May 2019. Then a 2.4 release came up after 1.5 years but this wasn't "upgrading" cleanly and had many migration issues. In fact, there are still migration issues pending upstream like 5197, 4820, 4979, 4821. We thus decided it's best to start "afresh" because it doesn't seem like the migration issues will be fixed any time soon.