danielemery / docker-react Goto Github PK

As per the title replace current circleci ci jobs with GitHub actions.

Main motivation is to make the project more approachable.

Currently when you deploy a new version of a docker-react app the browser caches the window.env.js file.

There are many ways this could be solved but the proposal I'm going with is to include a hash of the file's contents in the filename.

This will mean the index.html script tag will need to be updated each time the environment variables are changed, so this should be done as part of the npx docker-react prep command on container start.

This means this overlaps a little with #7

Include a flake.nix and lock to help developers using nix

• Sync the version of node with the flake version
• Also include a .nvmrc specifying the same version

zod is quickly becoming the leading option in the validation library space (when Typescript is in play).

Originally it was planned to support multiple forms of validation (rather than only Joi like now). However the complexity in providing separate Dockerfiles etc for each doesn't seem worth it.

Instead we should replace the Joi with zod and put plans to support other options (like Joi and yup) on hold until when/if the project is adoped.

Update the docker-react cli tool to be able to:

• Validate that each of the project setup steps have been performed
• Perform the project setup steps

The steps as documented in the README are:

• Install docker-react package and validation library
• Creating an environment variable schema
• Importing generated environment variable file into index.html (this has some overlap with #8)
• Creating a Dockerfile and .dockerignore
• Updating npm scripts
• Replacing references to build time environment variables with new window env

Single e2e test should:

• Bootstrap a new project with vite
• Apply all the steps in the README to the project
• Include an example of an environment variable being used
• Build the dependent project with it's Dockerfile
• Start the container
• Curl the container, validate that it serves the app and the environment variable has been correctly set