- 5 Posts
- 41 Comments
1·4 months agoThank you. Please provide any feedback on github issues.
Yes location, weather will be coming soon. There is existing feature request opened by the community for this. I am not sure what do you mean by routes. Can you provide more details as what such a feature will look like?
The documentation is fixed. The disable bit is by design. Once you disable signup all signups are disabled. You can still provision user in user management after logging in and then they can just sign up either through the password you set or OIDC. https://journiv.com/docs/configuration/user-management
They don’t have to. As long as Obsidian or any tool is working for someone then that is what they should use.
But for many including me Obsidian is not a solution for journaling although I extensively use Obsidian for note taking. You can read why here
Thank you. Looking forward to your feedback.
Thank you. I am glad to hear.
Thank you. Please provide feedback on github issues.
Thank you. Please provide feedback on github issues.
Thank you. You are right. Journiv Ahead sounds way better :)
Thank you. I am glad you like it.
The article and discussion here is about open source software which is not free software. Thats where the problem lies it is assumed that open source software has be free.
Freedom in software does not mean free software.
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.
Definitely!
Exactly for the reason you said. They don’t care about your privacy they want your verified email address to sell to the higher bidder.
Burning the midnight oil on my self hosted journal app: https://github.com/journiv/journiv-app
Import/Export are coming very soon! Here is sneak peek https://github.com/journiv/journiv-app/issues/92#issuecomment-3535960988 Built in a way that we can easily make and keep backup without fiddling with docker.
I am happy to hear that :)
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 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.
- 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.
Hello, yes it is.