Define the default ports (again)

[aschaeffer]

Follow up to #193 and #360

Because of the new architecture (Inexor Flex <-GRPC-> Inexor Core) and the possibility to run multiple instances (see #362) a typical Inexor installation uses multiple ports at the same time.

I would suggest these default ports:

Component	Provided Service	Default Port	Protocol	Remarks
Inexor Flex	Webserver & REST	31416	TCP
Inexor Core Client	GRPC Server	31417	TCP
Inexor Core Server	ENET Server	31415	UDP	see #193
Inexor Core Server	GRPC Server	31414	TCP	= ENET-Server - 1

We should define the default port only for the default instances of the server and client.

[Fohlen]

Using 31415 for the default core instance with both, gRPC and enet is desirable.. In a sauerbraten-manner, expanding 31416 as the default flex port is most elegant, imho.. If we think that strategy won't fit us (because of performance, complexity, whatsoever..), using a iterative approach with 31415, 31416, 31417, whereas the last is flex would probably suit as well..

[a-teammate]

We shouldnt rely on GRPC being tcp

[Fohlen]

I'll keep it gRPC port +1 for server port, since that is easier to remember for consequent instances of inexor. By that, 31417 shall be the standard port for Flex.

[Fohlen]

Any more discussion needed or can we draw a conclusion and make this a decision?

[Croydon]

Fine by me.

[Fohlen]

Changed due to consent. Updated in flex.

[aschaeffer]

1. We should add that information to the wiki, too.
2. The port 31415 can't be used twice (that wasn't my idea!), because I want to run a server and a client on the same computer at the same time without adjusting the default ports.
3. I would prefer that port 31415 is used for ENET of an Inexor Core Server because that's the most noticeable port.

[Fohlen]

Narf narf, can we close this?

[aschaeffer]

Yes