I’m new in this forum, but I’ve been using dawarich very successfully on my Synology NAS for about a year now.
Without this app, I would never have thought of tracking my location history. Unfortunately, I couldn’t get past version 0.25.8 because there were changes at the time that I couldn’t implement.
Now that so much has changed, family location, Android app, etc., I would like to try an update.
Unfortunately, the instructions refer to docker in the shell, which I cannot find in syno. I do have a Portainer.
Can anyone help me find the right approach to upgrade my version 0.25.8 to the current one?
I started with dawarich 0.2xx.x and always selected the latest image in Container Manager. With the switch to 0.26.0, it is necessary to convert the PostgreSQL database from 14 to 17. I did not do this due to a lack of knowledge, and the containers no longer started. My approach at the time was to switch from the latest to 0.25.8. In hindsight, that was not a smart decision.
Now I wanted to take another look at the issue. I stopped the project and performed a complete backup of the four containers and the database. Then I opened docker-compose.yml and created the entry for the service and the volume. According to the instructions at Updating to PostgreSQL 17 with PostGIS | Dawarich , step 2 is to create a dump of the database via the console. Now don’t laugh at me, but which console do I have on the Synology?
Perhaps one option would be to set up a new project and re-upload the database, but to be honest, I want to manage the update.
Is it an option for you to try and proceed without updating Postgres? If you have a backup from PG14 you can try simply update Dawarich without upgrading Postgres. It should work with no issues database-version-wise
Compare your compose to the one from the next version and made appropriate adjustments, or just follow the updating guide, the changelogs always contain instructions on how to update in case of breaking changes
But I’m following the instructions, which say to create a dump of 14 and upgrade it to 17. Trying without this database upgrade results in this ugly screen.