I am sharing my conclusions in the hope that they might help someone else too.
Importance of Splitting Wikis
During migration, I discovered several tiddlers that were not correctly tagged, tags that were not reachable from the table of contents, and tiddlers that should have been in the system path.
Even if you are not facing a performance issue, splitting wiki into smaller wikis is good practice once you have collected several tiddlers on a subject. It helps improve the internal structure of your notes and remove redundant tiddlers.
View/Update multiple wikis
I decided to use TidGi to manage all my wikis. It runs wikis using NodeJS and presents them in a single window. Hence, I will not have to switch between different windows looking for a specific wiki, and I can keep getting the advantage of the NodeJS server.
It has bugs. But so far, they do not seem showstoppers, though I hope the developer will make the app more reliable.
Syncing configuration and plugins
One solution is to export all your settings as a plugin. Eric has a great tip for creating plugins from your tiddlers.
But I already store my tiddlers using a custom file path configuration.
[is[system]!has[draft.of]removeprefix[$:/]addprefix[_system/]]
So all my settings are inside the _system folder. All I had to do was to copy these three into new wikis to replicate the configuration
- tiddlywiki.info
- plugins
- _system
Interlinking Wikis
For now, I am going to rely on localhost links, like, http://192.168.10.3:5217/#2022-10-01
If getting a permalink to a wiki is critical, then the only solution is to store or host it at a permanent domain name, like wiki1.mydomain.com. But for now, the localhost URL is OK for my needs.