Plugins on nodejs

[Tiago_Sanches]

Excuse my ignorance, but how do I install plugins on my Node.js + TiddlyWiki server? I’ve already successfully installed some, working as needed, with SSL…

Unofficial plugins, like the wonderful TW5-Graph…

I saw this link: Installing Plugins on TIddlywiki + Node.JS: Help for Better Documentation

But I didn’t quite understand where I get the plugin files…

[Mirokko]

Basically, you can just drag and drop into your instance of TW and thats it. Plugins no more than bunch of tiddlers.

[Tiago_Sanches]

So, is it just a matter of adding (drag and drop) it, like in a simple TiddlyWiki HTML file?

What are the specific instructions for Node.js (client-server configuration) for, like here:

Installing Plugins on TIddlywiki + Node.JS: Help for Better Documentation

There is difficulty in installing plugins on Node.JS, specially for new comers! This wiki post is an invite for collecting comments/ideas/instructions for simpler installing and working with plugins on Tiddlywiki + Node.JS . I have been using the below instruction. For example for new Section Editor Plugin [img_577_chrome] [img_578_chrome] If still needs further help, then open another tiddler: [img_579_chrome] [img_580_chrome] [img_581_chrome] [img_582_chrome] See the full doc here: …

Install Third Party Plugins: Standalone (single html) and Client-Server (Tiddlywiki on Node.js)

This wiki post describes how to install third party plugins in Tiddlywiki. Instruction have been given in the below links (As sample Section Editor has been used for demo) Install plugin on standalone and client server configuration Installing Plugin in a Single Html File Installing Plugin for Tiddlywiki on Node.js More on Client-Server Installation References 1.https://tiddlywiki.com/#Installing%20custom%20plugins%20on%20Node.js 2.https://tiddlywiki.com/#Environment%20Variables%20on%20No…

tiddlywiki. com/#Installing%20official%20plugins%20on%20Node.js

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

What would be the difference between dragging and dropping, and creating the “plugin” folder with the plugin inside it?

[linonetwo]

Simple answer:

1. drag & drop from plugin demo site
2. install from plugin library or CPL

Long answer:

Installing Plugins on TIddlywiki + Node.JS: Help for Better Documentation

Just come across this again via google search, so I answer this again: 1th of all, recommend my tiddlywiki app https://github.com/tiddly-gittly/TidGi-Desktop , which is an opensourced Obsidian alternative, where all plugins are installed via clicking “Install” button. It starts a nodejs tiddlywiki instance, but you can choose enable or disable http server, so protect privacy even in open wifi area. And secondly: Don’t put plugins to pligin folder & update tiddlywiki.info, it is not recommen…

[Tiago_Sanches]

Thanks linonetwo. I’ll go that route. Manually modifying the configuration files as little as possible.

I have another question. In Node, everything is saved in .tid files… I noticed that when deleting an annotation, it correctly deletes the file, but when deleting, for example, a plugin, some remnants remain. For example, to do these tests, I deleted cpl, but files like “$_config_Plugins_Disabled$__plugins_Gk0Wk_CPL-Repo.tid” and “$__plugins_Gk0Wk_CPL-Repo_config_current-repo.tid” remain (even after restarting Node).

Is there a correct or appropriate way, manually or through a plugin, to delete these remnants that will no longer be useful?

[linonetwo]

@Tiago_Sanches

some remnants remain. For example, to do these tests, I deleted cpl, but files like “$_config_Plugins

As in the name, they are config files. Just like in Windows, when you delete an app, it may leave some config files in your account’s Document folder; so next time when you install it, your preferences will be preserved.

If you think that’s an issue, you can raise an issue in the TiddlyWiki github repo, so they could add an option when deleting config data—like when importing things—to delete all its related config files. This problem relates to the fact that all configs should have a constant prefix, so they can easily be found by the program.