Paul, Please look around at the various implementation and hosting opportunities with TiddlyWiki, I suspect you will get closer to an answer if you do that. The Save and Hosting subject is a big one in TiddlyWiki given browser compatibility and future security changes.
Perhaps voice why you asked in the lead question, fill out your use case and there may already be a solution. If you ask specific questions your are more likely to get specific answers, however it sounds like you are seeking a general or systematic solution. Regards Tony On Tuesday, September 12, 2017 at 12:56:06 AM UTC+10, Paul P wrote: > > This is of interest. https://noteself.github.io/ I cannot run CouchDB > however maybe I can use the same concepts. > > So far I am uncertain as to the best approach to take. Because of the size > of even an empty tiddlywiki I am leaning toward storing each as a separate > file on the server upon save of the wiki. I am thinking this helps ensure > each tiddlywiki is "future proof" because each is fully self contained. > Newer versions of tiddlywiki will not affect older versions. > > However this is all new to me and so I may be mistaken on some basics. > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bfdc30e9-3d9c-4349-9009-df512b9a0cb1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
