Actually there is an easier way than replacing the folder. Just set
_datafoldertarget
property in settings.json to whatever folder you want to use. The plugins
are bundled so they load faster. It doesn't matter, TiddlyWiki just loads
them either way.

On Wed, Sep 11, 2019 at 5:16 AM mauloop <maul...@gmail.com> wrote:

> Hi, Arlen.
>
> I would like to upgrade the TW version included in TiddlyServer to 5.1.21,
> which fixes lot of 5.1.20 bugs. I think I could simply download the new TW5
> rel from Github and replace the tidllywiki subfolder in the Tiddlyserver
> install dir.
>
> I noticed that all of the plugins, themes, languages, as well as the core
> itself, provided with Tiddlyserver are packaged as bundles (the
> plugin.info files) that include the plugin metadata and all of the plugin
> tiddlers, while those coming from the official Github repo are made of
> folders containing many .tid files. I imagine that you choosed the bundle
> format due to some performance issues.
>
> Is it correct? Should I care about this while upgrading TW5 rel? How can I
> repackage TW 5.1.21 as you do with the 5.1.20 included in Tiddlyserver?
>
> Thanks in advance,
>
> )+(
>
> --
> 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 tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/42630cef-8bb6-4100-b7c4-51b5e192e024%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/42630cef-8bb6-4100-b7c4-51b5e192e024%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQP21mGjP6qHAFO3JQFmW86NbfzxuvXLqGzkqn0bhhKGg%40mail.gmail.com.

Reply via email to