Tip for serving TW5 on node to local network

[Jim Lehmer]

Just a quick tip - most of you might already know this. In my scenario I have a TW set up to run under node. It is on Dropbox, and depending on what I am trying to do I may run it on either one of my Windows or Linux boxes. But I want a single command to be able to run it on either without change and I also be able to browse to it from anywhere on the local network, not just on the same machine (in other words, I don't want to run it on 127.0.0.1).

The secret is instead of doing ipconfig/ifconfig and binding the server to the specific IP address of your box, simply bind to 0.0.0.0:

tiddlywiki --server 8080 $:/core/save/lazy-images text/plain text/html Jim "" 0.0.0.0

Works great, and now I don't have to worry about what machine I launch it on.

[Tobias Beer]

What's different between 0.0.0.0 and 127.0.0.1 ...except from a few digits?

Best wishes, Tobias.

[Matthew DeAbreu]

The default command will run and listen on 127.0.0.1, in other words only the machine running the server will be able to connect to it. By running and listening on 0.0.0.0 it will listen on all network interfaces and will accept connections from any machine on the local network and not just from the machine running the server.

[Tobias Beer]

Thanks, Mathew,

Makes sense.
Surely a good idea for trusted networks.

Best wishes, Tobias.

[Tobias Beer]

Sorry for misspelling your name.

[Matthew DeAbreu]

No problem, glad I could help. As a note about security, if you have the server listening to 0.0.0.0 on port 8080 and in your router configuration have forwarded that port the server is open to all traffic on both the local and external network.

[Tobias Beer]

Added the lot here...

http://dev5.tiddlyspot.com/#expose%20node%20server%20to%20local%20network

Best wishes, Tobias.