To help myself stay sane in a world of continuous deployment and be able to effectively debug strange situations I wanted to tag every version of my app with version information, such as the commit hash, commit message, build date and more. My setup is one where I run an react app created using the
create-react-app CLI tool, deployed within a Docker container which is built using Docker Hub (using the Autobuild feature).
To be able to tag information there are two things you need to do:
Dockerfileto include environment variables
The addition of a custom build step is a seemingly undocumented feature with Docker Hub which I only found out due to this response on a GitHub issue. The gist is that you’d need to create a
hooks/build file from the same folder as your
Dockerfile in which you can specify the way your docker container is built. This overrides the way your container build is configured within Docker Hub, but can be made in a way that it cooperates;
#!/usr/bin/env sh docker build -t $IMAGE_NAME -f $DOCKERFILE_PATH .
For a more complete and minimal example regarding the possibilities with custom build steps; check out this repository on GitHub (thibaultdelor/testAutobuildHooks).
It’s also this build step where you can define additional arguments to be available during the build step. Something which is not the case by default. Here are some examples of arguments I have added;
date -u +"%Y-%m-%dT%H:%M:%SZ"``
Note that as a precautionary measure I have encapsulated the environment variables within a double quote (
"), which is required to properly deal with potential spaces in the values represented by an environment variable.
In order to give your React app access to the environment variables there’s still the need to modify the Dockerfile. For each variable you will need two additional lines;
ARG REACT_APP_BUILD_DATE ENV REACT_APP_BUILD_DATE $REACT_APP_BUILD_DATE
The first one defines what variables can be defined using the
--build-arg arguments on the
docker build command. The second line makes these variables available to the app during runtime, from which the node environment can pick these up. For more in depth details on the differences between
ENV, dive into this StackOverflow thread.
👉 Do you like what I'm writing? Sign up to receive new content straight into your mailbox!