Use .env file correct

[cworf91]

Summary The compose files can use variables from the env. file. At the moment we have variables like "image" hardcoded in the compose file. In the furture this variables should be resolved trough the .env file.

Details At the moment we replace the variables in compose files with envsubst. This should´t be done. The variables should resolved by the framework.

Acceptance criteria [ ] Compose network is runnung with variables [ ] OSCM is working as expected

[cworf91]

To start the proxy via compose-network, it´s now mandatory to make the call from the directory where the .env file is located. There is no way to workaround this, because it´s a limitation of the compose framework: "Compose supports declaring default environment variables in an environment file named .env placed in the folder where the docker-compose command is executed (current working directory)." (https://docs.docker.com/compose/env-file/) Therefore, the documentation has to be adapted in the Operators guid on page 19. It has to be mentioned that the compose commands must be executed from the directory where the enviroment (.env) file is located. Further more, the command: docker-compose -f docker-compose-proxy.yml up -d and docker-compose -f docker-compose-proxy.yml down has do be changed to docker-compose -f proxy/docker-compose-proxy.yml up -d and docker-compose -f proxy/docker-compose-proxy.yml up -d

[SuessI]

Changes to documentation will be made for release 19.1 in:

• QuickStart Guide
• Operator's Guide
• online help