I am happy to hear that :)

Cool. Makes sense. Can I request you to open a issue on github to track this? Thanks.

Thanks! My main focus right now is simply building the product, the license doesn’t matter much if the product itself isn’t good yet. It’s always easier to move to a less restrictive license later than to go the other way, so this is the approach I’m starting with.

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.

Thank you.

You can if you can run docker on it. As of now that is the documented path. It is possible to run it without docker but that need some documentation.

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?

Yes, mobile clients are coming. I want to have adoption and sustainability before investing time and resources in launching mobile clients. That is the reason why they will come little after. There has been lot of interest and appreciation for the app as you can see in github issues so stay tuned.

Thank you. Best of luck.

Thank you.

Thank you. Yes, desktop native app, mobile apps. All are planned and will come. Cross platform support was important to so people can run it on all platform. Hence the frontend is in Flutter which for most part is cross platform.

Although this so far have been hundreds of hours of work and there is much more upcoming to build it so as of now I am trying to make this project sustainable so I can continue working on it and it develops to the shape I want it to be.

Stay tuned!

Well one thing I know is no ads in the app :) Can’t stand them!

Awesome!

That is the answer I am seeking. If you have any suggestion/recommendation I will love to hear it.

Understood about docker. Yes, those are planned and on roadmap. Apps will be coming soon. But software takes effort and time and just to get it here I have put in hundreds of hours and there is much more to build. Currently my focus is to make the project sustainable so I can continue developing it.

Thanks.

Thank you.

Yes definitely. This is a very good feedback. Its surprising how being a developer and self hosted enthusiast who is neck deep on hosting everything of my own I completely forgot that there will be people who will like to use this and not know about docker and all the stuff (very common thing in self hosted community).

I would love to guide you through installing and using the application and your experienced feedback would definitely be very helpful in improving the app.

Are you on discord? Then you can join Journiv’s community discord server https://discord.com/invite/CuEJ8qft46 if you aren’t then just send me a message here.

No not rude at all :) All this is a good feedback. If the lack of documentation confused you then I am sure there are many others who will get confused for the same thing. It is definitely something I should improve upon so everyone can understand the project and use it if they want to.

Cross platform for various reasons. There are two parts to Journiv

1. Backend: This is what you run on your local machine (ideally a small server/nas) which can run docker. You can run it on any machine.
2. Frontend: As of now this is a web app which you can run any where. The frontend of Journiv is in flutter which is cross platform and allow native desktop and mobile apps. Mobile apps will be launched soon.

Can I ask if you have ran/used docker before?

Thank you.

Journiv is source-available but not “Free Software” under the FSF/OSI definition. I chose the PolyForm Noncommercial 1.0.0 license intentionally to keep the code open for personal and educational use which allow hosting for non-commercial while preventing “commercial” redistribution or hosting for commercial gain without permission.

My motivation behind Journiv is to give a solution to self hosted people like me and other a journal first experience on par with any major cloud offering so that they don’t have to mold their usage to a notes app and be unsatisfied and frustrated like me. This license enables everyone in the self hosted community to use Journiv.

I did consider permissive and copyleft licenses (Apache, GPL, BSD, etc.), but sustainability is a major concern for this project. I have already spent hundreds of hours on this over last couple of months and there is so much more to build (take a look at the issues page of github repo). I want to keep development open and transparent while ensuring that commercial entities can’t simply repackage and profit from it.