Migration from single HTML file to Node.js

[anthrospeak]

What is the easiest way to migrate content from single HTML to Node.js? Thank you!

[digitalap3]

here is a command to take the tiddlers and put them into a folder. tiddlywiki --load ./mywiki.html --savewikifolder ./mywikifolder

Start up a new nodejs TW : tiddlywiki mynewwiki --init server , from here.

move tiddlers from mywikifolder to tiddlers folder in Nodejs wiki directory.

Alternatively you could start up the nodejs server and drag and drop the single file to it then choose which tiddlers to import!

[JanJo]

It would be great to have a Videocast on this process. It seems to be easy, but none fhe less I always had a feeling of having missed something.
So I stick to the single file version for years though node definitely has advantages.
Can I still Drag and Drop Plugins to a node.js=implementation?

[telumire]

Depend but for official plugins the doc recommend to edit the tiddlywiki.info file like this :

..
    "plugins": [
        "tiddlywiki/tiddlyweb",
        "tiddlywiki/filesystem",
        "tiddlywiki/highlight"
    ],
..

See https://tiddlywiki.com/#Installing%20custom%20plugins%20on%20Node.js

[TW_Tones]

@JanJo I would just add that on node and bob etc… Implementations you can add plugins to the server or the independant wikis. For example a one off plugin it may be easier to install it in one wiki and all you favorites in the server.

How many wikis you expect to build in that node instance over time may also influence you choice.

At least in bob you can always export a site to a single file wiki even without the command line.

[arunnbabu81]

@JanJo

It would be great to have a Videocast on this process.

It would be a great, if someone could make a video on installation of custom plug ins in node js. I guess drag and drop also works. But I have never succeeded in installing plug ins as told in the TW documentation. May be this can be inspiration for @pmario next YouTube video.

[pmario]

@JanJo

Can I still Drag and Drop Plugins to a node.js=implementation?

@JanJo Yes, but they are part of the “content”, so they will be stored in the /tiddlers/directory.

[pmario]

@arunnbabu81

But I have never succeeded in installing plug ins as told in the TW documentation. May be this can be inspiration for @pmario next YouTube video.

It’s not really possible to create a video, that matches the docs. I have had a closer look to the docs and it needs to be re-structured.

The different elements are correct but there is some duplicated info, which has subtle differences. So it’s confusing for new users.

• There are probably 3 ways to install plugins to single-file wikis
• There are at least 3 more ways use plugins in a node-js environment

The node and single-file plugin handling needs to be clearly separated. At the moment the info is mixed. That’s why you probably had trouble to do it right.

I’ll try to create a PR with a new structure this weekend using: 7 Steps to Improve the TiddlyWiki Documentation

[JanJo]

@pmario

There are at least 3 more ways use plugins in a node-js environment

I ask myself whether there is a difference which plugins should be installed with paths in node.js and which plugins can be installed as

@pmario

part of the “content” (as said here)

For example I noticed that the uglify-plugin can make specific use of such an installation (the changes than are reversible) Is this the case with other plugins as well? It would be great to have an overview here.

Another question I have regarding node.js is how compatible it is with php files.
For example I have some files which allow users to upload files and store them in directories in the same folder as my single wiki index.html.
Would such a contruction be still possible?

[pmario]

There is a pending PR at Github … Once it is merged, it will be possible to record some videos, that show how to deal with the different plugin installation methods.

You can import this JSON file to tiddlywiki.com and start with the Plugin tiddler and the changes made recently shown in the Recent tab. … The problem is, that working with plugins and a client-server configuration needs some more explanation.

PR-restructuring-plugin-install.json (23.6 KB)

[pmario]

@JanJo

Another question I have regarding node.js is how compatible it is with php files.
For example I have some files which allow users to upload files and store them in directories in the same folder as my single wiki index.html.
Would such a contruction be still possible?

Sure, but for plugin you have to have a defined directory strucute, that is described in the PluginFolders tiddler. For eg: Image files it depends on the server settings, if it’s possible to serve them

[TW_Tones]

@JanJo

For example I have some files which allow users to upload files and store them in directories in the same folder as my single wiki index.html.

I would love to know what you are doing here and how you do it.

[JanJo]

Hi @TW_Tones here this is off-topic but we can continue this thread.

First steps in PHP - uploading a tiddler

On a request in another thread, I will share here some hints to get started with PHP. I may not be he best guide in this territory, but there is still rather few TW-specific information on this. If you are used to the fantastic foolproofness of TW, with PHP you should know what you are doing because on your server a harmless sounding command like unlink can be a planetary killer. The other danger is that you want to allow people to put files on your server, which always was a little spooky to …

[pmario]

@arunnbabu81

It would be a great, if someone could make a video on installation of custom plug ins in node js. I guess drag and drop also works. But I have never succeeded in installing plug ins as told in the TW documentation. May be this can be inspiration for @pmario next YouTube video.

Here you have it

New HowTo Playlist: Use Plugins with TiddlyWiki and Build Single-File Wikis using the CLI

Hi folks, I did just publish a new playlist on my YouTube channel: https://www.youtube.com/c/pmariojo with some HowTo’s about TiddlyWiki and Plugins Subtitle 1: Use plugins with a single-file wiki Subtitle 2: Use plugins with a client-server configuration using Node.js Subtitle 3: How to build a single-file wiki using the “tiddlywiki” command line In the first 4 videos I talk about how you can install plugins from the Standard Plugin Library and from 3rd Party Plugin Libraries. I recommen…

Discussion about Node.js plugins and environment variables start at video 11. If you start with 12 you’ll miss important stuff.

I recommend to start at video 1 … I think it’s worth it

[arunnbabu81]

Thank you @pmario. I saw your videos from the beginning (5 to 12) and it was very informative. It’s good that you kept each concept as short videos rather than a single lengthy video. Even though I knew the basic things of using node js wiki, it’s was interesting to see how an experienced user cum developer is using node js wiki - learned some new tips from those videos. Installation of plug ins was the most wanted part of this video series and you did it nicely and precisely. I didn’t get time to test what I learned from your videos which I will do shortly and come back with my doubts. Link to this video series could be added to the official documentation about the node js wiki I guess. There are more in interesting videos in your YouTube channel, some of which I have seen in the past. Thanks for all your contributions to the tiddlywiki project.

I had commented in one of your video (my YouTube profile name has an extra n than the one used in this forum)

[buggyj]

In short: you can install plugins in exactly the same way in node.js as in a single file tiddlywiki - I cannot see any downside to this - and it is EASY.

I do not see the point in installing plugins as directories if the plugin does not add functionality the the node.js instance. - I have written many plugins - they are released as ‘packaged plugins’ - ie. as a plugin tiddler. It is possible to run these plugins from directories but you would need to know how to check their repositories out of github and then branch the resulting repositories to the correct version.

Different plugins may need different paths - on widows I have never gotten this to work with more than one path.

[vuk]

I did it the opposite way after reading the help for tiddlywiki Node.js program:

1. tiddlywiki mynewwiki --init server
2. tiddlywiki mynewwiki --load path/to/file.html

where file.html is another wiki with just one tiddler which I exported from another Node.js wiki as described here https://tiddlywiki.com/static/Installing%20TiddlyWiki%20on%20Node.js.html

Btw documentation calls it “making an offline copy”, while I prefer calling it “exporting” (in context of working with the Node.js version). Then the question asked in OP can be named “importing” - so I get a small logical namespace for describing going back and forth fluidly between single file and Node.js in my mental model. For this reason I also think that the help page I linked to above must cover the import from existing single file wiki in an additional point 6. Or at least have a link if the process is described somewhere else in the docs.

But going one paragraph back, I’m noticing that my workflow is one step shorter - I don’t manually copy any directory with tiddlers - it’s already there after the second command succeeds. Since I saw the test tiddler appearing in the new wiki, I concluded I did it right (for the first time though). Now that I found this recipe, I have to ask what’s the difference and which workflow is the correct one.

[linonetwo]

Ask normal user to use terminal is a torture.

Simply download https://tidgi.fun/ , and use its “Import HTML wiki” and “Export as HTML”.
Only two mouse click.

[vuk]

Excuse me, but somehow you managed to showcase the Y-X problem twice in one post.

[linonetwo]

Because I created TidGi and it is great and free, I want more people to use it.

And it solve the problem here.