On Sat, Sep 27, 2014 at 12:16 PM, PMario <[email protected]> wrote: > On Saturday, September 27, 2014 10:14:59 AM UTC+2, Jeremy Ruston wrote: >> >> It would certainly increase flexibility if we added a plain static web >> server to TW5 under Node.js. Two things are needed: the ability to suppress >> a tiddler from being included when building the TW file, and the ability to >> GET individual tiddlers in their raw form. >> > > If you want to serve static content, the advise everywhere on the web is: > use an existing server that does exactly that, is battle tested for many > years, and put it in front of the nodejs app. Why invent a new wheel, with > a system, that's designed for a different usecase. I'd suggest nginx. It's > a well documented small footprint web server and rides the wave atm. >
Yes, that would definitely be true for Internet facing deployments. What I'm suggesting is pretty much a quick and dirty way of adapting TiddlyWiki's existing HTTP serving framework to permit serving raw (unwikified) content. So it doesn't change much overall. Best wishes Jeremy > > -mario > -- Jeremy Ruston mailto:[email protected] -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
