Provide OSCM as standolone setup using default ports

[GoebelL]

Summary OSCM applications require different ports to be exposed on the docker host. In a common deployment only default ports are available. OSCM shall be deployed in a way that all applications are accessible with default ports.

Details A reference solution already exists (ask me). Idea is to add an nginx webserver in front of the OSCM docker network that operates as reverse proxy and exposes the applications on default TLS port.

Acceptance criteria

• [x] All applications: oscm-portal, oscm-app, oscm-app-*, oscm-rest-api and mail are accessible from client browser without an port specification
• [ ] All applications and internal redirects are working properly

Additional context Ask me

[uhu133]

Please also provide a (IP-address customized - if neccessary) home page with URLs for (probably not complete):

• APP admin

• APP VMware admin

• APP xyz admin

• APP process overview (restart processes)

• MailDev Mail Container

• OSCM Homepage

• Documentation

• Issues ...

[cworf91]

The proxy is deactivated by default. To start the proxy container, navigate into your installation directory and start the compose network: docker-compse -f docker-compose-proxy.yml up -d. To stop the proxy use: docker-compse -f docker-compose-proxy.yml stop.

[GoebelL]

@cworf91 For the oscm-proxy the deployer copies the keypair files in same ssl directory. This is different from other containers, and causes that custom key paths with chain certificates cannot be imported. Also the layout does not match with the documentation. Please correct this to have a unique layout.

How to fix: In docker-compose template the cert, chain and privkey must be mounted separately, in same way like the SSL files mounted in the oscm-core container. Currently on the parent folder is mounted. Don't forget to adapt the copy statements in the deployer start script.

[SuessI]

Documentation updated for ESCM 19.0 and distributed for review