Do you mean more info on the reverse proxy approach?
Basically you put a webserver (like nginx) in front of other servers and expose them with a certain configuration.
For example nginx running on public-1:80 serving internal-1:8080 from /custom-app and internal-2:8080 from /flowable-ui.
This would mean that you can access ‘custom-app’ resources from ‘flowable-ui’ and still having the ‘same origin’.
In addition to this you can have additional configuration on these mappings. Like manipulating headers;
(When using dockerized services; there ‘docker aware’ reverse proxies available; like Traefik. These can provide some OOTB convenience)
Hope this helps.
Yvo