• 2 Posts
  • 29 Comments
Joined 8 days ago
cake
Cake day: November 11th, 2025

help-circle
  • It’s funny how common this mindset is in the self-hosting community: “If I’m running it on my own hardware, the software should basically be free… maybe I’ll toss a tiny ‘tip’ if I feel generous.”

    The logic seems to be that since there’s no ongoing server cost, the developer’s time, skill, and effort must somehow be worth nothing and that we should magically fund the entire project through some hypothetical cloud version that they themselves will never use.

    It’s like showing up to a brewery with your own growler and expecting the beer to be free because you didn’t use their glass.









  • 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.