[!CAUTION]
Update 02/15/2026: Day One Import is broken in beta.17 release. You must use earlier beta.16 to do an import from Day One and then follow migration steps below.
[!CAUTION]
Beta.17: Introduces updated format of handling entry content. Now journiv stores entries in standard quill delta format
You must backup before upgrade and perform migration actions after upgrade if you care about your entries.
What's Changed
Journiv Beta.17 brings complete backend based draft support, markdown typing mode and bug fixes for immich media handling while editing existing entry.
Upgrade Steps
1. Make Postgres DB backup
This will dump your database backup to file named in journiv_full_backup.sql in current working directory. If you are using sqlite then you can just copy the sqlite db file to a safe location.
Make a Journiv export of you journals as back up. You should select "All Journals" and you would need to ask all user on your instances to make the export (if you have multiple users). We will keep this as a secondary backup but the guide below prefer direct docker backup and restore.
3. Stop all Journiv containers
This step will vary depending on your setup and how you run containers.
docker compose down
4. Update Journiv version
Update your Journiv version to 0.1.0-beta.17 docker tag.
5. Start all Journiv services
docker compose up -d
Note: After starting your services if you open your browser and see you entries you would not find any entry content. This is expected. Perform the below migration to migrate your entries.
10. Migrate the journal entries
[!CAUTION]
You must backup as suggested above before migrating.
Now go to Journiv in browser and spot check your journal entries to be showing up as expected. You can do this over couple of hours or days. Once you have ensured that there are no issues in displaying journal entries run the following command to clean up older format.
Note: You must do this clean up step before upgrading to any future versions of Journiv.