4lch4/node repository overview

⁠Node Docker Image

• Parent Image⁠
• Docker Hub⁠
• Git Repository⁠
• GitHub Action⁠

This image is the one mentioned in the initial example, and it starts with the official Node image⁠ that's tagged as lts⁠ and then adds the Doppler CLI⁠ so it can be used for secret management.

⁠When/How Often Is It Updated?

The image is built⁠ using GitHub Actions⁠ and pushed to Docker Hub⁠ when any of the following events occur:

• When a new change was pushed to the remote repository.
• Once a day when it's 08:00 UTC or 02:00 CST.
• When a developer kicks off a manual run via the GitHub UI (aka workflow_dispatch).

⁠Using the Doppler CLI

In order to use the Doppler CLI you must pass a Service Token⁠ with, at least, read access to the config you wish to use. Here is an example:

docker run -d --name=doppler-test \
            -e DOPPLER_TOKEN="doppler-service-token-here" \
            image-name-here

NOTE: I also created a CLI app⁠ to do this for you. If you're interested, I cover it in the following section.

⁠CLI Utility

• Git Repository⁠

As mentioned above, in order to use the Doppler CLI you must pass a service token with at least read permissions for the config to be used. To make this easier, I've created a small CLI application, Doppler And Docker Starter (dads), that will run a docker image that uses Doppler under the hood. Once it's installed on your machine (instructions need to be added) you can start a container like so:

#dads <app-name> <img-name> [doppler-token]

# Start a container named app-name-here with the image-name here Docker image.
# The lack of a doppler token option means the app will search for a .env file
# in the current directory and try to pull a DOPPLER_TOKEN variable from there.
dads app-name-here image-name

# Starts a container using the image-name Docker image, names the container
# app-name-here, and uses doppler-token-here as the Doppler Service Token.
dads app-name-here image-name doppler-token-here