[EPIC] Docker Compose "Aura Web"

This docker image should provide a NGINX Configuration with following aspects in mind:

• Reverse Proxy for Sterring at "/admin"
• Reverse Proxy for Dashboard at "/"
• Reverse Proxy for Tank at "/tank" and to work with Dashboard (similar to how @jackie set up the previous Apache at https://aura-test.o94.at)
• Reverse Proxy for Studio Clock at "/clock" ("Dashboard Clock", engine-clock#12)
• Redirect URLs so that authentication of Dashboard and Tank is working against Steering
• Reverse Proxy for public APIs of Engine only (TrackService API only, Reporting API tbc with @jackie, StudioClock should stay hidden). Keep in mind that Engine API should be protected as DOS Attacks when accessing the API. Engine is using Gunicorn as the production API Web Server and here are tips on how to make those two communicate with each other: https://medium.com/@thucnc/deploy-a-python-flask-restful-api-app-with-gunicorn-supervisor-and-nginx-62b20d62691f

Background Info: This Docker Compose depends on the Docker Images "Steering", "Dashboard", "Tank" and "Dashboard Clock". These Docker Images will run on the same hardware instance. Infos on the suggested setup: https://gitlab.servus.at/aura/meta/-/blob/master/docs/installation-guide.md

added To Do label

changed the description

mentioned in issue dashboard#41 (closed)

changed title from Docker Image "Aura Web" to Docker Compose Image "Aura Web"

added EPIC label

added P1 label

added 1 deleted label

Beside the need to discuss the overall structure of Docker and Docker Compose images, I suggest we also discuss how we start the images in dev and prod context. The run.sh in each and every project has already some basic concept (mainly for dev & needs to be improved). We can expand on that.

added discuss label

mentioned in issue #23 (closed)

assigned to @jackie

changed milestone to %Aura 0.9

added Doing label and removed To Do label

@jackie Please note that "Engine Clock" (engine-clock#12) has been missing from the description above. It should be served similarly to the "Dashboard Docker". Adding it now to the description above..

changed the description

I've created a (temporary) aura-web repo: https://gitlab.servus.at/aura/aura-web

This is so I can get a setup running in a clean environment, before integrating it into the meta repo.

So far still WIP. But could be done in May. Locally a proof of concept is already running. Will test it on aura-test as soon as I have integrated let's encrypt into the nginx container.

@jackie To me it's still unclear how the mechanics work in combination with #21 (closed). Because at the Hackathon in July at Marreith you mentioned you now would like to keep it as a separate "aura web" repo in contrast to providing all the maintenance scripts from a single repo like "meta" (as suggested in the comment above).

Additionally: As discussed via chat, please ensure the run.sh scripts are working locally in each project individually and via the Docker Composer codebase as well. Please check to keep the codebase DRY among repos, meaning that the specific maintenance/run.sh code is not simply duplicated into the Docker/Compose code, but only called from there. Hence the project specifics should be kept (or refactored back, as you suggested) to the individual projects.

assigned to @nnrcschmdt and unassigned @jackie