HI,
The TiddlyWiki --listen command has a lot of additional parameters. See: TiddlyWiki — a non-linear personal web notebook
tiddlywiki “path/to/wiki” --listen host=10.1.x.x should do the trick.
-m
Ah! I knew it must be something easy - thanks for that! Lots to read up on 
If node is set to 0.0.0.0 the IP address becomes server on the LAN at the current (or all) IP address(s) of the device.
On windows you can actually configure additional IP addresses on your desktop, and then rather than use 0.0.0.0 use the specific IP address. I have done this on bob but got it mixed up a few occasions. The smart trick is to assign an additional IP address outside the dhcp range and host your server on that but from your desktop. One day you may move your server and the additional IP address to another computer, say onto a NAS, server or always on computer - even a raspberry Pi.
Another nice tip is you can use any 127.X.X.X address on the local host as well so you keep 127.0.0.1 free for other services.
I can elaborate, I am just hinting here.
Regards
Tones
Brewed idea has fermented into a different prototyping project.
Scenario:
Say I have two sales reps, each with his/her own TiddlyWiki running on node.js
They each maintain their own customer lists, but I want each sales rep to have view-only privs on the other sales rep’s customer list. So that each Sales rep can be a backup to the other one when a Sales rep in on vacation or whatever.
Each Sales rep should have a directory of his/her own customers, but also have available a global directory of all customers (so merging of the directories.)
And those directories should provide a way to see customer details, regardless of the source (Sales rep’s own wiki or other sales rep’s wiki.)
And a way to know when something new has happened in the other wiki.
All without having to learn new technical things, other than familiarizing myself with basic TiddlyWiki and node.js stuff.
The current scope of naughty bits
Playing around a little, here are some of the things that will be involved:
-
WebServer Basic Authentication, WebServer Authorization, WebServer Parameter: credentials
-
Maybe: This goofy approach to dynamic HTML/javascript creation in an iFrame
- A way to know about “what’s new” (re customer info) in other Sales reps’ tiddlywikis
-
Enhanced tiddler saving actions for a customer to update a “customers list” data tiddler
- Each sales rep has a “customers list” tiddler, and each sales rep has a symbolic link to all other sales reps’ “customers list” tiddlers; so a “list of customers” tiddler brings in, formats, sorts, all of these data items from all of these data tiddlers
-
won’t be super-perfect because each tiddlywiki needs to be restarted to get the latest data tiddlers from the other tiddlywikis
Something like that. No fuss, no muss. Keeping it simple.
-
won’t be super-perfect because each tiddlywiki needs to be restarted to get the latest data tiddlers from the other tiddlywikis
- Each sales rep has a “customers list” tiddler, and each sales rep has a symbolic link to all other sales reps’ “customers list” tiddlers; so a “list of customers” tiddler brings in, formats, sorts, all of these data items from all of these data tiddlers
1 Like
Based on a cursory review of your scenario, I think it can be generalized to Real Estate applications. This opinion is based on my discovery that Agents frequently share their listings with other Agents ( even ones from competing Brokerages ).
It could be even more general if a Seller and several potential Buyers were inclined to share some of their property data. Since my views are mostly Canadian, I can say that this has considerable potential in competing with CREA ( the Canadian Real Estate Association that runs virtually all of the Canadian MLS = Multiple Listing System )
Best,
Hans