On Tuesday, August 20, 2019 at 11:35:29 AM UTC+2, Xavier Maysonnave wrote:
>
> It is orthogonal to the saver mechanism which is concerned with saving the 
> entire HTML file as a single file.
>
>>
>> The two mechanisms are pretty much independent: one can be syncing 
>> individual tiddlers to a server and then simultaneously use the saver 
>> mechanism to save a snapshot of the entire wiki.
>>
>
> If I understand correctly. The save button call a saver (are the savers 
> chained in case of multiple setup, eg gitub, gitlab...? ) while the 
> syncadaptor is dynamic and reacts to events ? If its correct I like the 
> mechanism as it gives users a way to easily backup their wikis.
>

Savers are _not_ chained at the moment. ... But they could and imo should 
be, if we would change the code accordingly. 


 
>
>> One crucial difference is that the syncer mechanism requires an external 
>> process to build the HTML file. That is done dynamically in the default 
>> client server configuration: the route `/` triggers a build of the entire 
>> wiki. It can also be done by an external build process that periodically 
>> rebuilds the HTML file.
>>
>
> I'm not sure to understand here. I think this is why I'm lost. While 
> studying the syncadaptor I didn't get any understanding about how the 
> remote stored wiki has been initialized in the first place and this is why 
> I was thinking about my described mechanism. Load a self contained wiki. 
> Setup the ipfs target and then use the syncadaptor to push the contents to 
> IPFS.
>

It is possible to create a syncadaptor that can handle single file 
tiddlers, that works with IPFS if the browser can access the API needed. 

I did create a proof of concept some time ago, with an outdate version of 
beaker-browser, which allows me to write to a DAT archive, with single file 
tiddlers. 

have fun!
mario

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev/f16c261b-15a6-496e-83d7-17fd3584d93e%40googlegroups.com.

Reply via email to