Scott, Yes you can, and I did so previously. However whatever you install, it may be a tiddlywiki server, or AMMPS LAMP MAMP or some other server they typically use port 80 or 8080 on 127.0.0.1 out of the box so a chance of a clash is high. You thus have to manage it.
Bob will grab the next port but the local links will need to change if the port changes I moved to additional IP addresses for on my lan so I could establish a DNS entry for Bob as an example on its own IP address. If later I move Bob to another computer I just move the additional IP Address as well and it will continue be at the same address. However this breaks down on a new network, without the same DNS or network This solves the new network and local host problem by moving the server to 127.X.4.X fixed address, so it works no matter the network on my laptop and will only be available on the LAN if I am on the "correct" network I have not done it yet but I believe I can set it to be available on the LAN using one of my "Additional" IP Addresses however multiple servers will always be locally available with the custom 127 address's and will use whatever port they want with no need to increment up to an available port. Is that a little clearer? Regards Tony On Wednesday, April 1, 2020 at 3:40:24 PM UTC+11, Scott Kingery wrote: > > Hi Tony, > Can't you just use different ports? 127.0.0.1:8081 for something and > 127.0.0.1:8082 for something else? > > Maybe I'm missing what you are trying to do. > > Scott > > On Tuesday, March 31, 2020 at 8:28:29 PM UTC-7, TonyM wrote: >> >> Folks, >> >> I was exploring various alternatives for the local host addresses in Bob, >> TiddlyServer and I expect what I found would be the same for node installs. >> >> Problem >> >> - Normally on my home LAN my Bob and tiddly server are accessible on >> the LAN >> - To keep it tidy and so it did not interfere with my DHCP (fixed) >> network address I defined more addresses on my Network adaptor >> - Eg Desktop 192.168.1.119 (DHCP) TiddlyServer on 192.168.1.81, >> Bob on 192.168.84 >> - I have shared this tip previously >> - However when I connect to another lan like my hot spot these >> addresses are on the Wrong Network eg 192.168.3.X and do not work even >> just >> locally. >> >> Discovery >> >> - I discovered IPv4 network standards reserve the entire address >> block 127.0.0.0/8 (more than 16 million addresses) for loopback >> purpose >> - Which made me aware that 127.0.0.1 is not the only available local >> host address >> >> Tip/Solution >> >> - This means more than one instance of TiddlyServer and Bob/Bob.exe >> can be set to a local host address, >> - This leaves 127.0.0.1 free for hosting other servers. >> - I tested this and it works well eg I use 127.0.4.80 127.0.4.81 >> 127.0.4.82 127.0.4.83 127.0.4.84 >> >> Extension >> >> - I hope that I am be able to configure TiddlySaver, Bob and Node to >> Share on the addresses 192.168.1.80 - 84 in addition to the local host >> address >> - This will only work when I am on the 192.168.1.x network >> - When on other networks such as 192.168.3.X or some shared network >> such as my "hot spot" they will not be available on the LAN >> - In my browser, on the computer hosting the servers, I will always >> use the different local host addresses, and they will always be available >> when the computer is on any network but private unless at home / >> 192.168.1.x networks which means I time I may change this. >> - Further investigation of The Internet Assigned Numbers Authority >> (IANA) which has reserved 169.254.0.0-169.254.255.255 for Automatic >> Private >> IP Addressing. As a result, APIPA provides an address that is guaranteed >> not to conflict with routable addresses. >> >> Regards >> Tony >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b3c8546b-91e2-49af-a663-cede1dabd46c%40googlegroups.com.
