Cloning a wiki with its plugins, settings, etc, but without the content

[Dani Zobin]

Hi,

I have a Tiddly, and want to create another one, for other topic.

How can I clone my wiki with all the technical stuff inside (plugins, settings, etc ), but without the content?

Thanks

Dani

[HansBKK]

> How can I clone my wiki with all the technical stuff inside (plugins, settings, etc ), but without the content?

Depends on how complex your "design" component is - in my case very, so I build with this capability in mind.

I always do my "design-level" work - that isn't specific to the user-specific content - in a "master empty" TW file, and then either import the content from the old container into a new instance, or keep the "children" TWs in sync with their "parent".

Just make sure that you use a tagging convention - mine is ".system" ".content" and ".meta". The latter is for things like maintenance tiddlers with tools like GroupByPlugin, ShowAllByTags, MatchTags TagGrid et all, and the tiddlers providing navigation. So ".system" can be bulk over-written from the empty to the children files, .content is master in the children (including local-only content-specific tags as opposed to system-level tags), and I need to think about what comes over in the .meta category - lately I've started to use ".metalocal for those tiddlers that are always changed locally (search results, ImportedTiddlers report, content-tag specific maintenance tiddlers, etc.

I also maintain a "master repository" to keep my plugin collection up to date and sync'd across all my TWs, and have multiple "content-tag" repositories for indexing taxonomies that are shared between multiple TWs on related but separate topics - see here

Using ImportTiddlersPlugin's "filter" capabilities makes the whole thing much easier, although in some cases I use LoadTiddlersPlugin.

sample syntax: tag:[[!.content && !.metalocal]]

If the real gurus here have less labor-intensive methodologies they're willing to share, I'm all ears 8-)

[Måns]

Hi Dani

> How can I clone my wiki with all the technical stuff inside (plugins,
> settings, etc ), but without the content?

Eric (tiddlytools.com) has made two plugins which output optional
content from an already existing TW:

SaveAsPlugin: http://www.tiddlytools.com/#SaveAsPlugin
info:http://www.tiddlytools.com/#SaveAsPluginInfo
and
ExportTiddlersPlugin: http://www.tiddlytools.com/#ExportTiddlersPlugin
info: http://www.tiddlytools.com/#ExportTiddlersPluginInfo

Cheers Måns Mårtensson

[HansBKK]

Correct me if I'm wrong, but you'd still need to have your content tiddlers tagged separately from the "system" ones to use with the filter option unless you were going to select them all manually. . .

[Måns]

Hi HansBKK

> Correct me if I'm wrong, but you'd still need to have your content tiddlers
> tagged separately from the "system" ones to use with the filter option

> unless you were going to select them all manually. . .*

I would tag all changed shadowtiddlers, plugins, systemThemes etc.
with a unique tag.
It would make it easy to collect a new empty document with the same
features as the original from a single tag...

I would use the filter option in saveAsPlugin or use the "apply
filter" option in ExportTiddlersPlugin...

Cheers Måns Mårtensson

[HansBKK]

Thanks Mans, that's exactly what I use my ".meta" tag for. Since my "base" is usually an already well-populated and tweaked flavor of TW, like MPTW or more recently TWT-Treeview, I tag all those tiddlers ".system".

Then I use .content for everything I would want to strip out if I were saving an "empty".

Then ".meta" covers new non-content tiddlers for features like siteTitle, menu nav hierarchies, tag-checking, zzConfig etc. These three tags should include every tiddler in the document (one aspect of tag-checking tiddlers).

Works well for me so far, but I really like the idea of doing a "Save As" to create a new empty rather than trying to maintain a separate "master empty" - that way whatever content-populated "child" I'm working on becomes the new master.

Then it's relatively easy to use ImportTiddler to update the other "sibling" files - now that I'm also using ".metalocal" for the ones that *always* change for every file.

[Dani Zobin]

Thanks guys, 

This all  makes sense, and thank you for pointing me to the plugins by Eric. 

Will use this as I have some time to mess with my new wiki

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.

To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/cFU5Y4fn-NoJ.

To post to this group, send email to tiddl...@googlegroups.com.
To unsubscribe from this group, send email to tiddlywiki+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.