In fact @Michaelsy, you are perfectly right: this simple solution accomplishes what i really want, which is "inclusion" (in the non-technical sense that they are transparently accessible) of large files in my wiki, without compromising either one of (a) performance of the wiki, AND (b) portability. This is why i don't really want to go node.js, because that's just not as portable as a single file, or directory of universally-readable files. So thanks for pointing out the most elegant solution to this problem (hiding in plain sight, as it were :-)
On Saturday, July 4, 2020 at 9:47:17 PM UTC+1, Michaelsy wrote: > > The whole thing seems much less mysterious to me than the term "integrated > static file server" seems to suggest. After all, there is always some kind > of "file server", namely the software that makes it possible to make the > tiddlywiki.html file available to the browser. This could be for example > the web server of a provider, the web server or the file system of a local > computer. > > This: [ext[./files/a-big-document.pdf]] is simply the relative link to a > file, relative to the address (URL) of the tiddlywiki.html file. That > means, no matter where the tiddlywiki.html file is stored, create a > directory named files next to it and save the a-big-document.pdf there. > (Only the file permissions are still of interest. These should be identical > to the tiddlywiki.html file.) > > But since I'm not really sure I've overlooked anything essential, I would > be happy to receive feedback. > -- 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/eca7ca8f-72f9-447f-9043-ffc4a8aa81c2o%40googlegroups.com.
