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.

non-docker ways will come later. Stay tuned!

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.

Hello, Thanks for your interest. It is possible but a little work as it will require one to have Python interpreter installed and do few things to run it. Yes, thise instructions are not there. I will add them. Do you have Python installed?

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.

No. There are feature requests to add support for imports from various places. If you plan to use the app please open an issue.

Thanks.

Please read the documentation linked in the ReadMe and you can try out all the security features.

There are docs for auth model, the code around it, the limitation of in-mem tokens, the clear documentation around token handling, the code to support CORS, trusted host middleware, CSP, HSTS, rate limiting. You can read the env.template and configure and try it out. I doubt there are self hosted (vibe coded, ai-assisted or even non vibe coded) existing apps which have these security feature in v0.1 or even later.

Like mentioned in comment and ReadMe the project is written with AI assistance not vibe coded or AI driven development. If you will read the code, look at design and db model you will find the answers you are seeking. Having said that I am always looking to make the project better so if you find anything which can be improved please open a PR.

Thank you.

Thank you.

Thank you.

Thank you. Yes, as a software engineer, not using AI for tasks where it can significantly accelerate development would be unrealistic. Much of the boilerplate code such as database ORM models, serialization/deserialization logic, and documentation was written with AI assistance, as mentioned in the project’s README. No developer writes such consistent and complete API docs :D. The architecture, UI/UX and harder aspects (see below) are done by me. It took me 2 months of late nights (hundreds of hours so far) and spending every minute outside of job and family on this and without AI would have taken much more. What you see now is the result of many iteration, refining the UI/UX, redesigning the database, and reworking the overall architecture, flighting with CORS configs make video player work on web in flutter etc etc… much of which isn’t visible from the outside.