Hi, Tony I achieve "use several location to store tiddlers" today.
I'm now saving my private tiddlers in a folder A, which is a git repo that can push to a Github private repo. And some another tiddlers is in another folder B, which will push to another public github repo. I use https://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming to place tiddlers tagged with a "private" tag to be store to the folder A. See https://wiki.onetwo.ren/#%24%3A%2Fconfig%2FFileSystemPaths for example. 在 2017年10月7日星期六 UTC+8上午10:06:36，TonyM写道： > > Folks, > > Sorry about the narrative approach to this Question, it is in part because > I am still climbing the TW5 learning curve hill/mountain. It relates to > more advanced uses of NodeJS, but not core or plugin development > (necessarily). > > *Background* > I have implemented most tiddlywiki Hosting platforms as I learn more and > Prepare for Firefox 57. I have NodeJS running on my Windows Desktop, My > Synology NAS, My Mac Mini, Android phone and tablet. all Great stuff. > TiddlyServer also allows me "serve" both TiddlyWiki files (including those > I can also host through ISS WebDav, and Node Installs off the same address > and Port. > > Now I indend to migrate a 17Mb TWC into multiple TW5's, build my own > plugins (later), Tiddler Bundles, TiddlyWIki Solutions and editions. > > *I have a lot of ideas so if someone wants an interesting project just > ask.* > > I have done a rudimentary search and not found any documentation for using > the multi-file tiddler structure of Node JS such that it may be able to > support me on this journey into tiddlywiki as an environment, and even then > what I find documentation is more about contributing to the core, or > serious plugin development, something I hope to do one day, but I know my > limitations. For now I want to see how I can exploit the *NodeJS* > solution to help *manage a complex environment.* > > I have explored and continue to explore drag and drop, import export, > bundles and building (rudimentary) plugins. However I have now a multitude > of File based tiddlywikis and there are management issues. In fact some of > the solutions I plan to develop relate to managing multiple file based > tiddlywikis. But I expect NodeJS may help me. > > *The Question(s)* > > - *Can anyone point me to some resources on using NodeJS in more > sophisticated ways?* > - *Is what I am thinking possible?* > > > 1. Can I create a set of structured folders that NodeJS will search to > build TiddlyWiki editions, such that I can place shared tiddlers or > plugins > in a one or more locations that some editions use and not others? > 2. Imagine for example I have say project related TiddlyWikis and > Task Management TiddlyWikis, could both point to plugins and Tiddlers > they > Share, but other editions do not? > 3. or a Folder of Snipit tiddlers the Editor uses that all Wikis > can access, > 4. if I updated a plugin or shared tiddler could the different > wikis now all see the update? > 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? > 6. Could I have a library of plugins I collect that I can > selectively refer to? > > *Because I do not know what I don't know, this Question is very broad, > perhaps once I have a little more detail I can start new threads on > particular methods.* > > *Please note: I have a very systematic way of looking at things and love > re-usability, de-duplication, maximising possibilities and minimsing > compromise.* > > Thank in Advance > Tony > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/50200cdf-bbf9-495f-8f56-e64316e7d178%40googlegroups.com.
