I can’t give you nearly as much detail as some people can this topic but I can tell you that the basic concept is that the demo version no longer stores its information in a series of markdown files. Instead it stores everything in an internal database.
Where that databases or even if it’s accessible to us I’m afraid I can’t say. In their defence that website was never really designed for regular use so much as testing. I think we’ve begun to use it as a web app even though that wasn’t their original intention.
There’s been quite a bit of discussion about how to synchronize that database without using the paid for synchronization service. But perhaps synchronisation isn’t really what you’re after.
You should be able to export the entire graph if that’s of any use to you?
As far as I can tell, it must be using local storage in the browser (or similar). My main concern is data loss - if an update or security policy is pushed out that clears local storage, I lose everything.
I could periodically export, but that becomes a whole hassle that I don’t need to worry about right now.
Please don’t use the comments on this post for troubleshooting or bug reporting. There is another post that has instructions on how to do that. (Please don’t post bug reports in that thread either - instead, follow the instructions.)
I am using MD desktop version and want to try out the new DB beta. The question is can I have them both installed on the same PC? Or the new one will replace the old one once installed? It is kind of scary to test)))
it’s safe and easy to test. simplest way to go about conflict is to go to test.logseq.com/ and import your existing MD files. then play with it, creat backups of both, and then transition to the DB if you want to!
Right now you might have an issue with the two desktop apps having the same name. (They are going to rename the MD app to avoid this.) However, you can get around this limitation by using the web app to test Logseq DB, as user jar has said above.
