• 3 Posts
  • 30 Comments
Joined 3 days ago
cake
Cake day: November 11th, 2025

help-circle







  • Thank you for adopting Journiv! Yes the export will be added. I do agree with you that a human accessible export is very important. I am a software engineer who knows how to make docker backups etc etc but I never do it :) I know I can set it be automated but the friction is too high to do it.

    Journiv is being built for out of need and to be the solution of owning memory so it long term strategy is at it’s core. I am personally using it for all my memories with my young family so it will be devastating to lose it because of backup friction.

    My plan for Journiv is:

    1. 1 Click export which periodically created a static HTML site with all the entries and media. Zips it and put in local location configured by user. Since journiv run in a docker container the first phase will be putting it but not tied to docker container lifecycle. Second phase will be integration with a network file share where Journiv can automatically dump the export. Once I configure it I want it to just work not fiddle or worry about making backup. If backup fails I get some discord/telegram notification or within Journiv app.
    2. Flat JSON export with media. HTML static site will allow user to see entries but JSON export is critical so that the entries can also be exported some where else if the need be.



  • Thanks. Export will be added pretty soon. As of now you can export entries in PDF as that was one of the most requested feature. Since the beauty of self hosting is that all the data lives on your machine. You have it with you all the time. It is just a database (sqllite or postgres) and all your media files under a directory. Back up is pretty simple you just backup the docker volume or the bind mount directory which is standard for docker.

    Although I do want to add a more human accessible export output which people who do not want to deal with db can use.

    What kind of export would you like to see?