Port offsets

46 views
Skip to first unread message

Stuart Douglas

unread,
Jul 28, 2021, 9:00:32 PM7/28/21
to Quarkus Development mailing list
Hi Everyone,

I was thinking that it might be a good idea to create a global port offset config value.

Basically you can do -Dquarkus.network.port-offset=10 and every port number would be increased by 10 (including the debugger port). This would make it easier to run multiple services locally without port conflicts.

Every extension that binds a port would need to handle this manually, but there are not that many of them and it is very simple.

Does this seem worthwhile?

Stuart

George Gastaldi

unread,
Jul 28, 2021, 9:17:45 PM7/28/21
to Stuart Douglas, Quarkus Development mailing list
+1, this is really useful in envs running two quarkus apps 

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAD%2BL2czyMB8STuHv-G-WUUpFr%3D3DhTXARnOXM5Xde0hroz6b5g%40mail.gmail.com.

Stephane Epardaud

unread,
Jul 29, 2021, 3:51:18 AM7/29/21
to George Gastaldi, Stuart Douglas, Quarkus Development mailing list
What ports are we talking about, BTW? It would be very useful to collect the ports that extensions bind to in a build item and report them at startup, and add them to https://github.com/quarkusio/quarkus/issues/17808 for initial reporting, and perhaps generate a docs page which lists them too.



--
Stéphane Épardaud

Emmanuel Bernard

unread,
Jul 29, 2021, 5:08:45 AM7/29/21
to Stephane Epardaud, George Gastaldi, Stuart Douglas, Quarkus Development mailing list
Does that include port offset of client side things? The question behind that is whether it's only on the "server" side and then what would be the interaction with a server like Kafka (unlikely port change) and a server like another Quarkus instance you aim to connect to as a client side. Let's make sure we walk through these scenarios when port offset is designed.

Stuart Douglas

unread,
Jul 29, 2021, 5:13:48 AM7/29/21
to Emmanuel Bernard, Stephane Epardaud, George Gastaldi, Quarkus Development mailing list
I think just server, or at the very least they should be separated into different properties.

We also have an item about unifying SSL configuration, so if we are doing common network configuration options we should consider this as well.

Stuart

Sergey Beryozkin

unread,
Jul 29, 2021, 10:46:13 AM7/29/21
to Stuart Douglas, Emmanuel Bernard, Stephane Epardaud, George Gastaldi, Quarkus Development mailing list
I found a similar approach be very useful when starting a standalone Keycloak server

Sergey


Reply all
Reply to author
Forward
0 new messages