Dockerfile for Dashboard Clock

added To Do label

changed milestone to %Aura 0.9

added P2 label

mentioned in commit 38ac797b

assigned to @david

@jackie I've added an initial implementation https://gitlab.servus.at/aura/engine-clock/-/commit/38ac797b2dac1d33690913c5297f088e746a86b7 for running Engine Clock with Docker, based on your dashboard/Dockerfile. I'm not quite sure about the next steps on how to integrate the multi-stage build into run.sh (some stubs are there) and in your final Docker Compose. No hurry btw., just a reminder for us to chat about it.

added Blocked label and removed To Do label

Assigning to @jackie in case further Docker Compose modifications are needed.

assigned to @jackie and unassigned @david

added To Do label and removed Blocked label

assigned to @nnrcschmdt and unassigned @jackie

assigned to @david and unassigned @nnrcschmdt

removed To Do label

changed milestone to %1.0-alpha2 — Precise Pheasant

changed title from Dockerfile for Engine Clock to Dockerfile for Dashboard Clock

changed the description

changed milestone to %Aura 0.9

added Doing label

closed

removed Doing label

I've updated the Dockerfile to include two targets with the following behavior:

Dev - target

In the dev-target the image exposes port 5000 and runs ./run.sh dev - thus running the development web-server.

Prod - target

For the prod-target the files for the deployment get generated via ./run.sh build. The files then are copied into an image derived from nginx and get deployed via that nginx on port 80.

Reverse proxy

Since this issue is mentioned in https://gitlab.servus.at/aura/meta/-/issues/7 under "reverse-proxy": in the dashboard-container I've added the option to act as a reverse proxy for the dashboard-clock. It then gets deployed under /clock.

PS: I didn't realize this issue was already closed. I'm sorry for the necrobump.

@EorlBruder super, thanks!