Multi-Wiki Server

#1

Polling interested (technical) parties.

When using the new Node.js Multi-wiki Server (stock or websocket/Yjs real-time), would you want to configure the new tiddlywiki.info file property called serveWikis the same way as the includeWikis property. I.E. an object with a “name” value and a “path” value relative to the tiddlywiki.info file. OR would you want to have logic that searches the TIDDLYWIKI_EDITIONS_PATH environment variable, and the local ./TiddlyWiki5/editions directories?

There are benefits to both, as can be expanded on here.
-----><-----
Currently, my test setup uses a variation on the init command logic, in that it scans the TIDDLYWIKI_EDITIONS_PATHenvironment variable for the listed directory, and if not found THEN checks the ./TiddlyWiki5/editions editions (the init command has the opposite order-of-operations). With this you can get away with a one-line string serve, as my example tiddlywiki.info file shows with the “Empty” wiki, and you can use relative or absolute pathing (see “Dev”):

{
	"description": "Chronicles.wiki edition",
	"plugins": [],
	"themes": [
		"tiddlywiki/vanilla",
		"tiddlywiki/snowwhite"
	],
	"serveWikis": [
		{ "name": "SilatKilap", "path": "SilatKilap" },
		{ "name": "Test", "path": "Test", "readers": "Freyja", "writers": "Joshua" },
		{ "name": "Dev", "path": "/tw/editions/Dev" },
		"Empty",
		{ "name": "TWDocs", "path": "tw5.com" }
	],
	"build": {
		"index": [
			"--rendertiddler","$:/core/save/all","index.html","text/plain"]
	}
}
#2

Alternately, if we use the includeWiki style, you must provide the “name” (route) and “path” values, which it would look like:

{
	"description": "Chronicles.wiki edition",
	"plugins": [],
	"themes": [
		"tiddlywiki/vanilla",
		"tiddlywiki/snowwhite"
	],
	"serveWikis": [
		{ "name": "SilatKilap", "path": "../SilatKilap" },
		{ "name": "Test Wiki", "path": "../Test", "readers": "Freyja", "writers": "Joshua" },
		{ "name": "Dev", "path": "../Dev" },
		{ "name": "Empty", "path": "../Empty" }
	],
	"build": {
		"index": [
			"--rendertiddler","$:/core/save/all","index.html","text/plain"]
	}
}

:Edit: I am personally leaning towards this atm, it avoids a bunch of custom searchpath code, but relies on the User to get the “path” value correct relative to the “Root Wiki” folder.