vector-im-hydrogen-web/Dockerfile

FROM docker.io/node:alpine as builder
RUN apk add --no-cache git python3 build-base
COPY . /app
WORKDIR /app
RUN yarn install \
 && yarn build

FROM docker.io/nginx:alpine

# Copy the dynamic config script
COPY ./docker/dynamic-config.sh /docker-entrypoint.d/99-dynamic-config.sh

# Copy the built app from the first build stage
COPY --from=builder /app/target /usr/share/nginx/html
chore: optimise Dockerfile So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. 2021-03-08 17:02:04 +01:00			`FROM docker.io/node:alpine as builder`
Required pkg for aarch64 docker build 2021-09-30 04:31:39 +02:00			`RUN apk add --no-cache git python3 build-base`
chore: optimise Dockerfile So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. 2021-03-08 17:02:04 +01:00			`COPY . /app`
			`WORKDIR /app`
			`RUN yarn install \`
			`&& yarn build`

			`FROM docker.io/nginx:alpine`
Allow config override in docker image 2023-01-11 19:06:25 +01:00
			`# Copy the dynamic config script`
			`COPY ./docker/dynamic-config.sh /docker-entrypoint.d/99-dynamic-config.sh`

			`# Copy the built app from the first build stage`
chore: optimise Dockerfile So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. 2021-03-08 17:02:04 +01:00			`COPY --from=builder /app/target /usr/share/nginx/html`