Single File vs Node.js

[Qalisto]

As a noob who is now going full throttle on a PIM relocation BUT also as a non-coder, I wanted to ask ... IF  ... at some future point, I want to run certain TWs in concert with Node .js, will I have to do some massive reformatting in order to migrate the Single File variant to the Node variant?

If so, I may want to think this through very hard - now.

My preference is to have full portability as a single HTML.  This notion seems to be contradicted by the Node variant.

Can someone kindly point to the best explanation of "To Node or Not to Node"?  Like a decision tree??

==Q

[TonyM]

My only quick point here is you can move back and forth between both easily. You just need to control your work flow process. Such as which is your source of truth, can you merge them etc...

Extencive users of server based wikis may be able to raise some other issues but as far as I can see there are no risks with single file vs node and other server models other than your own failure to manage your wikis effectivly.

Regards
Tony

[Qalisto]

So, if for some reason I need the flexibility of node.js I can easily adapt a single file TW5 to the server variant?

[Jed Carty]

Yes, to go from single file to node you can either use a command line tool that splits a single file wiki into its components, or you can drag and drop the HTML file into an empty node wiki or you can use bob to do the conversion.

To go from node to single file there is a command line tool or you can just use the save button to download a copy of the node wiki as a single file. Bob also has a feature that lets you download a version of your wiki.with all of the nodejs components removed so it doesn't have unneeded plugins.

[Arlen Beiler]

The only problem you will run into is relative links. In single file wikis served as a file, your relative links will be to folders beside the FILE. When you move to the server, your relative links will be broken, because your relative links will be to folders beside the FOLDER. The best way to future proof your relative links is to put each wiki inside its own folder and name it whatever you want, but NEVER link to files inside the folder itself. In other words, your relative links should always start with two dots. You should put one wiki inside each wiki folder and you could call it index.html. 

This is the only problem I have been able to find. 

The TiddlyWiki node server does not support multiple data folders, but TiddlyServer does, and I think Bob might too but I’m not sure. You could also use an Nginx reverse proxy to do the same thing with the Node server, because the node server does support being mounted on a path. Sorry, that’s a lot of info in a short space. Hopefully it makes sense. 

Arlen

On Sun, Nov 24, 2019 at 03:17 Jed Carty <inmy...@gmail.com> wrote:

Yes, to go from single file to node you can either use a command line tool that splits a single file wiki into its components, or you can drag and drop the HTML file into an empty node wiki or you can use bob to do the conversion.

To go from node to single file there is a command line tool or you can just use the save button to download a copy of the node wiki as a single file. Bob also has a feature that lets you download a version of your wiki.with all of the nodejs components removed so it doesn't have unneeded plugins.

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7dbb398e-b846-4d54-8797-716f30facb8b%40googlegroups.com.