• 3 Posts
  • 22 Comments
Joined 21 hours ago
cake
Cake day: November 11th, 2025

help-circle


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














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



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




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