As many readers are in no doubt aware, my gun wiki environment is predicated on a master-slave arrangement. A Wiki Technical admin has a master copy of the wiki in which they maintain the various system tiddlers and tiddlywiki scripts. At the same time, a Wiki Content Master has the latest published version of the wiki file in which they maintain the content tiddlers.
So at some stage, we need to update the Wiki Content Master’s version to get them the latest system tiddlers, wiki scripts, etc. This is like the Upgrade facility for Tiddlywiki but using our own master version.
Has anyone done something similar? I can’t see how I can utilise the Tiddlywki Upgrade facility on our own master/slave wikis.
I assume the TW Upgrade facility uses some form a filter to dump out user’s content tiddlers and then reload them into a new copy of the TW master but I can not work out a filter command that does that. I can get individual tiddler types out, like system tiddlers, images, guns etc but am not confident that all are being exported successfully.
bobj
I have proposed a project that would be a superset of your Master-Slave wikis over here [RFC] A TiddlyWiki hub wiki architecture, but its not getting much attention at this point.
If you try and reverse engineer the upgrade facility you may find your answer there. Upgrade primarily updates the core “plugin” and deals with some, not all, contention between the existing wiki and the new version.
Thanks, @TW_Tones , I am playing around with more and more complex filters to try and come up with a filter that exports my content only so it can be imported into a technically new version. Slowly getting there I think…I hope.
Also playing around with date filters. I have setup a versioning system with each wiki storing a version number (actually the date of an upgrade) as part of its upgrade process. Now all I need is a filter that exports all changes to the Master after a given date (the version number).
Bobj
FYI: If you open an empty tiddlywiki did you know you can use import and open a full tiddlywiki (file) and import that?, it may not help you but it is possible.
I normaly use the upgrade process and I have semi-automated that,
but otherwise I would export a large JSON (avoiding core overrides) and import that to the new wiki.
Also if you do come up with a grand filter consider making a “filter tiddler” to reuse is perhaps create a filter tiddler (appears in the advanced search > filter > dropdown see SystemTag: $:/tags/Filter youi could create a bookmarklet of this filter tiddler for install anywhere.
@TW_Tones , thanks for your suggestion
I did not know that. I will have a play and see if that is all I need.
Bobj