Requesting support for a --ws_port launch flag (function analogous to the --port flag) #281
Description
I believe a --ws_port launch flag would be valuable for any users registering direct nodes, as any restarts could potentially change the ws_port of a node if other conditions on the server have changed. And if the ws_port changes, that requires a chain write to bring the address information into agreement with reality.
A hosting environment for kinodes would benefit greatly from this capability, as individual nodes on a serve will frequently be activated / deactivated / restarted, and we want to ensure that nodes continue to listen at the expected ports if possible.
The hosting environment will be responsible for knowing the expected port, and passing it into this new flag. It could be possible to approach this with the node recording "last used port" in its HOME and attempt to listen there, but I don't see any reason to make it different from the approach used by --port.