Hi Jeremy, Forgot to mention:
1) Installing sudo npm install -g tiddlywiki did not work on Windows 7: 'sudo' is not recognized as an internal or external command, operable program or batch file. That sudo part isn't that a Unix/Linux command? npm install -g tiddlywiki did work on Windows 7. 2) Upgrading The tiddler 'Upgrading TiddlyWiki on Node.js' at http://tiddlywiki.com/ says: sudo npm -g upgrade tiddlywiki Apart from the sudo part, the order (-g before upgrade), npm documentation [1] talks about update instead of upgrade: npm update [-g] [<name> [<name> ...]] The documentation at [2] does not contain an upgrade command. I found a reference to upgrade node.js via npm [3] but that is something different! I just did some searching; did not test anything. Cheers, Ton [1] https://npmjs.org/doc/cli/npm-update.html [2] https://npmjs.org/doc/ [3] http://davidwalsh.name/upgrade-nodejs On Thursday, January 2, 2014 9:07:40 PM UTC+1, Jeremy Ruston wrote: > > Thanks Chaps - I've updated the docs to use 127.0.0.1: > > > https://github.com/Jermolene/TiddlyWiki5/commit/2343bb3e5b57728f3321824ff278e2e2680e409e > > Best wishes > > Jeremy > > > > On Thu, Jan 2, 2014 at 8:00 PM, Ton Gerner <ton.g...@gmail.com<javascript:> > > wrote: > >> Hi Will, >> >> Thanks for sharing your experience. >> >> >> On Thursday, January 2, 2014 8:40:32 PM UTC+1, willw wrote: >>> >>> Hi Ton, >>> >>> I suspect that the failure with 0.0.0.0 is a Windows issue, so not >>> directly related to node. >>> >> >> I too think it is a Windows issue, but if ordinary users like me (just a >> TW user, no programmer) want to install node.js on Windows they ought to >> know 0.0.0.0 does not work. >> So, there ought to be at least a note with the install instructions of >> node.js. >> >> Cheers, >> >> Ton >> >> >>> >>> A couple of weeks ago, while installing TiddlyWeb on Windows, I saw >>> similar behaviour - Window's doesn't seem to serve 0.0.0.0 while Linux >>> is happy to. Did some searching, found similar experience but nothing >>> definitive. >>> >>> If it is true that Windows cannot serve it then 0.0.0.0 should not be a >>> default. >>> >>> My TiddlyWeb on Windows experience is reported on the TiddlyWeb Google >>> group. In short, Windows would never serve 0.0.0.0 while results with >>> 127.0.0.1 vs. localhost were inconclusive (behaviour on both Windows and >>> Linux was inconsistent, possibly due to some state being cached between >>> server invocations?). >>> >>> Will >>> >>> On Thursday, January 2, 2014 2:18:16 PM UTC-5, Ton Gerner wrote: >>>> >>>> Hi Jeremy, >>>> >>>> A long time ago I installed TiddlyWiki + node.js with help of the >>>> walkthrough of David Johnston [1]. >>>> >>>> Today I managed to install it according the new and easier way on 2 PCs >>>> (1 x Windows 7 32-bit, 1 x Windows 7 64-bit): >>>> >>>> npm install -g tiddlywiki >>>> tiddlywiki --server >>>> >>>> But >>>> >>>> http://0.0.0.0:8080 >>>> >>>> did not work with Firefox and Chrome. >>>> >>>> What did work was: >>>> >>>> http://127.0.0.1:8080 >>>> >>>> or >>>> >>>> http://localhost:8080 >>>> >>>> Cheers, >>>> >>>> Ton >>>> >>> > > > -- > Jeremy Ruston > mailto:jeremy...@gmail.com <javascript:> > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
