fraport/fradrive
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

build(docker/backend): envify PROJECT_DIR for runtime access

Browse Source
This commit is contained in:
Sarah Vaupel 2025-01-18 03:39:03 +01:00
parent 0ae8eddc5b
commit ecd0a443b4
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docker/frontend/Dockerfile
View File

@ -23,7 +23,7 @@ ENV NODE_EXTRA_CA_CERTS: "/etc/ssl/certs/ca-certificates.crt"
# locally these two should be identical, so that compilation results are written out into the file dir.
# in CI-pipelines these two should be different, so that the container caches the compilation results.
ARG MOUNT_DIR=/mnt/fradrive
ARG PROJECT_DIR=/fradrive
ENV PROJECT_DIR=/fradrive
RUN mkdir -p ${PROJECT_DIR}
RUN --mount=type=bind,source=.,target=${MOUNT_DIR},rw if [ "${PROJECT_DIR}" != "${MOUNT_DIR}" ] ; then cp -r ${MOUNT_DIR}/* ${PROJECT_DIR} ; fi
WORKDIR ${PROJECT_DIR}
@ -36,4 +36,4 @@ printf 'registry=https://pkgs.dev.azure.com/fraport/_packaging/packages/npm/regi
RUN make -- --dependencies-frontend IN_CONTAINER=true
ENV FRADRIVE_MAKE_TARGET=--compile-frontend
ENTRYPOINT make -- ${FRADRIVE_MAKE_TARGET} IN_CONTAINER=true CHROME_BIN=${CHROME_BIN}
ENTRYPOINT make -- ${FRADRIVE_MAKE_TARGET} IN_CONTAINER=true CHROME_BIN=${CHROME_BIN} PROJECT_DIR=${PROJECT_DIR}