Use less busy ports #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #49
What
This pull request simply changes the ports of the frontend and backend. I grepped for the old ports, I am pretty sure I found all of the references. This may affect the development workflow.
Backend: 5054 -> 15421
Frontend: 8081 -> 15422
As stated in the commit:
Available ports were found with a combination of looking up https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers , searching "port NUMBER", and looking up the speedguide.net information on the port.
Why
As explained in #49, 8081 and 5054 are commonly used ports in both production and development. Using those ports could easily cause compatibility issues with any other application that already uses them. The desired fix would be to have configurable ports, but a sensible default would be to use a less busy port.