i guess the true tw5 wiz could clearify if it's possible to change the location where tiddlers are saved, i know too little about how TiddlyWiki boot-up to change it myself (maybe it's not that hard since it should be possible to search for "tiddlers" in the source code...?)
it is in fact possible to startup TiddlyWiki on Node.js using:
$ tiddlywiki . --server
i.e. the
wikifolder is the current directory (the "working" directory), and everything works fine - though, tiddlers are still stored in the sub-directory "tiddlers" of the current directory. so, having the
tiddlywiki.info file and the executable in the same folder as the tiddlers would not make any harm at all - "it should work..." - and multiple wikis would not be any problem either since "Bob" create all "other" wikis in the sub-directory "Wikis" with it's own directory - a wikifolder for each and every wiki - with its own
tiddlywiki.info file as well.
well, i don't want everything to be in the same folder since i want to utilize
customising tiddler file naming - however, i don't want the "source files" (i.e. the "tiddlers") which *is* the wiki to be stored in a directory that is hard-coded(!) by the programmer - it should be up to the TiddlyWiki user to name the directory where all tiddlers are stored - i'm not that comfortable having multiple wikis stored together with a common parent directory, i usually want to spread my wikis on different devices, or in different directories on the same device which doesn't share the same nearest parent directory - the use cases for multiple wikis like "Bob" is designed are small, i think.
the main reason to be able to control what the "tiddlers" directory shall be named (well, for me the default directory should be the current directory - i.e. "./", if not configured by the TiddlyWiki user in the settings.json file) you can run a single instance of your wiki running as a CMS (Content Management System) which can be utilized in different ways, like a doxygen tool, like a source code review tool, like a "Jira" board for agile project planning, like a ticket system, like a bugzilla tool to keep track of the bugs in the source code, etc. i.e. every software development "project" could then utilize this CMS in different ways - but the same source of information will be stored in a hierarchy - and wanted data is easy to lookup with the built-in search tool in TiddlyWiki.
well, maybe you say: - this is already possible! ...if you put every "data" file and directories in the "tiddlers" directory - but still, i want to be in control where my "tiddlers" shall be stored - this is not something that should be hard-coded(!) by the programmer of TiddlyWiki... that's my opinion anyway.
however, we also need customising tiddler file naming to work before "Bob" could be dubbed the *ultimate* tool for TiddlyWiki :-)