Allow serving web interface and REST API on the same port #2446
Now that #2440 is merged, we can allow serving the web interface and REST API from the same port.
The suggestion is to allow setting the
Otherwise a second API service is started, which functions exactly as it does right now (i.e. separate port is bound, the two API services are different).
The current behavior should be the default to avoid surprises for current 2.0 users.
The text was updated successfully, but these errors were encountered: