Jed, Thanks Jed (PS I have a Nephew Jed) so much for that comprehensive answer, you have thrown a lot of light on this, By confirming some of my speculation you help me proceed knowing something is achievable, not me just dreaming again. It is great to get an overview from someone who has done it, and gets what I am looking for.
My Long term goal is to provide a resource for the tiddlywiki enthusiast and developer to build an environment that helps manage a number of tiddlywiki instances and shared tiddlers and Plugins. But for myself to start with. *On "5" Using this method could I have a tiddler store of Tiddlers that acted like a message queue that other wikis could use and respond to?* It looks like this is already workable except requiring the reload, I would love to hear some of your ideas on inter-wiki communication. It seems to me folders with JSON or TID files (Bundles included) with fixed names may be enough with the development of some in wiki ways to load them, then use tags or fields to identify tiddlers destined for the reading wiki and ignore the rest. I already have a skeleton of a process that includes identifying the source wiki (less clear to me in a NodeJS implementation you have outlined). I will collate your notes (others in this thread) and my own to build a resource that remains at the "usage and configuration level", and perhaps separately for the advanced development process. Ultimately I plan to publish this at http://tiddlywiki.psat.com.au Thanks once again Tony On Monday, October 9, 2017 at 1:11:46 AM UTC+11, Jed Carty wrote: > > I am going to try and write this up somewhere nicer with instructions that > hopefully won't require much knowledge. > > For those of you who are comfortable with node here is my setup: > > I am using the node version of tiddlywiki and I have it installed > globally, and I have TiddlyServer cloned from the GitHub repo. > > For plugins I have a folder that holds all my plugins, in my case this is > /home/inmysocks/TiddlyWiki/Plugins, this is set up the same as the normal > plugin folders are, so each plugin.info is in a sub-folder like > 'OokTech/BookMarks' and the tiddlers are organised normally from there. > > I have another folder that holds all my wikis, > /home/inmysocks/TiddlyWiki/Wikis, then each wiki gets a sub folder there > that holds the tiddlywiki.info file and has the tiddlers subfolder like > normal. > > Making everything play together nicely comes from the setup files, > settings.json for TiddlyServer and the various tiddlywiki.info files for > each wiki. I am hoping to make a utility that will help automate their > creation but for now it is all manual. > > For TiddlyServer I have the tree organised to point to all of the wiki > folders like normal, there isn't anything special that I do in > settings.json. To start TiddlyServer I have a bash script (I am not sure > what you would use in windows, it has been a long time since I used > windows, do .bat files still exist?). Here is the bash script I use: > > #!/bin/bash > > export TIDDLYWIKI_PLUGIN_PATH="/home/inmysocks/TiddlyWiki/Plugins" > cd ~/TiddlyServer > node server.js > pause > > Then in each tiddlywiki.info file for plugins I can just list the plugins > like normal, like "/OokTech/Bookmarks" for my bookmarks plugin located > at "/home/inmysocks/TiddlyWiki/Plugins/OokTech/Bookmarks", and this works > for any of the wikis served by TiddlyServer regardless of where they are on > my computer. > > Sharing tiddlers between different wikis takes a bit more setup. > > To make tiddlers from one wiki available in another wiki you edit the > tiddlywiki.info file for the wiki you want the tiddlers in. Add an > includeWikis section to the tiddlywiki.info file like the plugin section. > Here is an example: > > "includeWikis":[{ > "path": "/home/inmysocks/TiddlyWiki/Wikis/WikiName", > "read-only": "true" > }] > > I haven't found a way to selectively include tiddlers in another wiki, so > I found it best to have a bunch of small single purpose wikis that pull in > tiddlers from others instead of having a few big ones. TiddlyServer makes > that easy. > > One way to have wikis that are just specific bits of content is to create > the tiddlers in one wiki and save them to another one using > $:/config/FileSystemPaths, this is made simpler by having the different > wikis grouped together like I do. Then in the $:/config/FileSystemPaths > tiddler in one wiki you can put a filter like > > [tag[Other Wiki]addprefix[../../Other Wiki/tiddlers/]] > > which will have any tiddlers tagged with 'Other Wiki' and save them in the > tiddlers folder for another wiki. > > One example of how this can be useful is having a wiki that is used for > entering and saving bookmarks and then each bookmark tiddler can be saved > to another wiki folder which can then be included as read-only in multiple > other wikis. This can be used to have something like multi-user wikis. The > downside is that the server needs to be restarted in order to update with > the new files. Luckly adding ?reload=true to the end of the url when using > TiddlyServer. > > This can address 1, 2, 3, 4 (with reloading) and 6 > > I think that 5 would require changes to the server side. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7d5facb4-d04f-49c3-a78e-7e2a16c3282d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
