Generally, cloners are expected to do something like run `npm install` after clone to install dependency modules.
In the past, I have embedded tw5 under express by simply calling renderTiddler on a wiki module instance from a custom handler. This amounts to effectively eschewing the server.js command, and replicating much of its functionality in my handler. Tighter integration options for connect/express (or, more generically, node http servers of any sort) is something I think very worthwhile, and might explore. --Nate On Saturday, September 14, 2013 5:31:13 PM UTC-4, Javid Lakha wrote: > > (also, on GitHub, is it good practice to upload the modules one uses, or > are cloners expected to inspect the package.json file and deal with it > themselves?) > > On Saturday, 14 September 2013 22:29:21 UTC+1, Javid Lakha wrote: >> >> Hi Jeremy, >> >> I'm half way there with the proxy - I can require users to log in before >> the proxy displays TW5, but none of the changes persist. I'm trying to >> figure out why this is. Here is my code: >> >> https://github.com/javidlakha1989/tw5-auth >> >> (& yes, I realise the usernames and passwords will need to be MD5'd and >> the whole thing HTTPS'd at some point) >> >> Best wishes, >> >> Javid >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
