Such a wealth of options for Local-First storage have emerged in this 
thread (must say: i'm super impressed with the strength of this community i 
have just joined), i've been able to quickly implement the simple approach 
suggested by Jeremy (TW Desktop, + cloud sync to Github), which is serving 
me well enough for now. 

Yet, as i'm fast creating quite a mountain of data in TW, i'm also bothered 
by the growing sense that what i really want at the back end of this 
beautiful thing is a database -ideally SQLite, which has all that 
local-first/ single-file/ portability goodness of TW, while bringing the 
full set of functionalities needed to manage a large database with 
integrity.  With a single SQLite file stored locally and replicated to the 
cloud, that gives us a solution that ticks all the boxes in that seminal 
Local-First paper <https://www.inkandswitch.com/local-first.html>: Fast, 
Multi-Device, Offline, Collaboration, Longevity, Privacy, User-Control.  
Combining this with the power of TW5 interface (really an "interface 
builder for the rest of us," i would call it), minus mess of .html backup 
files i've got to keep cleaning off my machine (SQLite has a full 
transactional history, so no need of any backups but that one file, 
replicated to cloud), and that in broad-strokes would be the shape of my 
dream machine. 

So i must ask: has anyone tried using SQLite as storage for a TiddlyWiki?  
If this is indeed technically feasible, can anyone point me to prior art on 
which i might be able to build such a solution?  Though i am no programmer, 
i am reasonably comfortable with SQL as a data manipulation language, if 
someone can just show me how to get the TW data in there!

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/856ad777-dc63-4491-bd74-c0391c4bf413%40googlegroups.com.

Reply via email to