Refactor Dockerfiles and CI Configuration

Reconfigure Docker and overhaul the CI strategy:

• docker-compose has to spin up three images now, for database, frontend and backend. (Frontend container shall not have any access to database but through the backend)
• gitlab ci needs additional build stages for front and backend as well as more tests (jslint, UnitTests, etc).
• Dockerfile for frontend needs to be written.

changed milestone to %Creating the new project structure

assigned to @j.michal

added Blocking label

added CI/DC label

added Migration label

mentioned in issue #47 (closed)

changed the description

marked the checklist item Dockerfile for frontend needs to be written. as completed

marked the checklist item gitlab ci needs additional build stages for front and backend as well as more tests (jslint, UnitTests, etc). as completed

marked the checklist item docker-compose has to spin up three images now, for database, frontend and backend. (Frontend container shall not have any access to database but through the backend) as completed

Found a different solution. Since vue.js just outputs some static files no additional actual image is needed.

What is indeed needed is a new docker-compose setup for local-development and production. It is possible to have a setup with multiple docker-compose.yaml files that override and extend each other in order to prevent code duplications.

I consider this closed and will open another issue for defining deployment in the proposed way.

Closing commit via 047735d6 and aade6c6e.

closed