Skip to content
Deploy

fix: correctly set umami runtime env #2145

Sign in to view logs

fix: correctly set umami runtime env

fix: correctly set umami runtime env #2145

Triggered via push December 23, 2024 16:53
@MiniDiggerMiniDigger
pushed b82f117
master
Status Success
Total duration 4m 18s
Artifacts 2

deploy.yml

on: push
build
4m 7s
build
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: chart/dockerfiles/frontend/Dockerfile#L5
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: chart/dockerfiles/frontend/Dockerfile#L6
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes: chart/dockerfiles/backend/Dockerfile#L7
WorkdirRelativePath: Relative workdir "hangar" can have unexpected results if the base image changes More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
Legacy key/value format with whitespace separator should not be used: chart/dockerfiles/backend/Dockerfile#L9
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size
HangarMC~Hangar~4TWE87.dockerbuild
35.9 KB
HangarMC~Hangar~Y5FD1U.dockerbuild
35 KB