What's the deployment/backup situation here? If I understood it correctly, JournalBook doesn't persist data in a database or local files but rather in the browser (IndexedDb). This is fine but if you are using multiple browsers (because I'm running JournalBook on a server) then you can't sync between them.
For deployment, I created a Docker image: https://github.com/omarabid/docker-journalbook
Nothing sophisticated there, it just runs the website in a container.
Next step will be to have the data backed-up automatically but I'm not sure this is possible with the indexeddb solution. Are there any plans to support other storage types?
What's the deployment/backup situation here? If I understood it correctly, JournalBook doesn't persist data in a database or local files but rather in the browser (IndexedDb). This is fine but if you are using multiple browsers (because I'm running JournalBook on a server) then you can't sync between them.
For deployment, I created a Docker image: https://github.com/omarabid/docker-journalbook
Nothing sophisticated there, it just runs the website in a container.
Next step will be to have the data backed-up automatically but I'm not sure this is possible with the indexeddb solution. Are there any plans to support other storage types?