status-go
status-go copied to clipboard
[Browser plugin connector] Cannot launch multiple instances of Status desktop with same port for Websocket/RPC server
Problem
In development, developers are able to launch multiple instances of the Status desktop application. Use cases could vary from simulating chat between peers or more complex use cases requiring multiple instances of the status desktop application running. However, during this PR, enabling Websocket on a specific port would prevent other instance from starting since the port will be busy. This issue should be extrapolated to RPC server as well
Implementation
- Figure out a way to assign different Websocket ports for different Status-desktop instances
Acceptance Criteria
- Multiple Status-desktop are running
- Websockets are accessible as expected
Example test
Terminal 1
wscat -c "ws://0.0.0.0:<PORT_1>"
Terminal 2
wscat -c "ws://0.0.0.0:<PORT_2>"