vector-im-hydrogen-web/Dockerfile-dev

FROM docker.io/node:alpine
RUN apk add --no-cache git python3 build-base

WORKDIR /code

# Copy package.json and yarn.lock and install dependencies first to speed up subsequent builds
COPY package.json yarn.lock /code/
RUN yarn install

COPY . /code
EXPOSE 3000
ENTRYPOINT ["yarn", "start"]
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`
Required pkg for aarch64 docker build 2021-09-29 19:31:39 -07:00			`RUN apk add --no-cache git python3 build-base`
Install npm deps in separate docker layer 2023-01-11 18:55:28 +00:00
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			`WORKDIR /code`
Install npm deps in separate docker layer 2023-01-11 18:55:28 +00:00
			`# Copy package.json and yarn.lock and install dependencies first to speed up subsequent builds`
			`COPY package.json yarn.lock /code/`
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			`RUN yarn install`
Install npm deps in separate docker layer 2023-01-11 18:55:28 +00:00
			`COPY . /code`
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			`EXPOSE 3000`
			`ENTRYPOINT ["yarn", "start"]`