Skip to content

added frontend to allowed hosts #5

added frontend to allowed hosts

added frontend to allowed hosts #5

Triggered via push August 8, 2024 06:09
Status Success
Total duration 1m 12s
Artifacts 2

deploy.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
deploy
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-node@v3, actions/configure-pages@v3, actions/upload-artifact@v3, actions/deploy-pages@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "github-pages". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SECRET_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L9
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SECRET_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L10
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
github-pages Expired
520 KB
lostmypillow~jRAR~KY00P8.dockerbuild Expired
26.5 KB