Just a goofy thought: if I wanted to serve binary files so they don't have to be included in a TiddlyWiki instance, my first instinct would be to setup a ridiculously tiny web server for static content. (Any server similar to Web Server for Chrome <https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb?hl=en> or some tiny web server for Android.)
Well, that's one mindset of somebody who just uses TiddlyDrive. Crazy to setup some tiny web server if one is already setup with nodejs? Going wtih nodejs seems like a real no-brainer from a developer building TiddlyWiki-from-scratch angle. On Friday, July 23, 2021 at 7:08:52 PM UTC-3 PMario wrote: > Hi, > > I think the main advantage is, that you can easily build and test the > latest version of TW on your local PC. > It lets you serve binary files eg: images or PDFs from a /files directory, > so you don't need to include them in your wiki. > With the new SSE plugin mentioned in the other post it will allow a basic > multi user setup on the local network. > > It can be used to build different editions, that are shipped with TW eg: > empty.html, or the German version which is interesting for me ;) > It can be used to run tw5.com-server to improve the TW documentation and > create pull-requests to improve the docs at tiddlywiki.com > > So for me it's mainly a development environment and a playground for my > own wikis. > > -mario > > -- 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/822d4682-86eb-4a23-bdc6-566e63824319n%40googlegroups.com.
