improve behavior of docker containers and document local cypress testing

.gitignore

@@ -1,4 +1,6 @@
+.cache/
 .idea/
+.npm/
 chromedriver.log
 coverage/
 dist/

Dockerfile

@@ -0,0 +1,19 @@
+# https://docs.docker.com/engine/reference/builder/
+
+# In order for NGINX to consistently serve the docs directory the parent
+# directory (repository root) needs to be mounted because building the site
+# deletes and recreates the docs directory. If the docs directory itself is
+# mounted, the container will continue to serve an empty directory (resulting
+# in a 403) after it is deleted because it is mounting the original docs
+# directory and not the new one.
+
+# https://hub.docker.com/_/nginx/
+FROM nginx:latest
+
+RUN mkdir /app
+
+WORKDIR /app
+
+# Update the NGINX configuraiton to serve /app/docs
+RUN sed -e's#/usr/share/nginx/html#/app/docs#' -i \
+    /etc/nginx/conf.d/default.conf

README.md

@@ -69,14 +69,31 @@ website](https://www.docker.com/products/docker-desktop) and follow the
 installation instructions.
 
 
+### Startup containers
+
+The containers can be started with:
+```shell
+docker compose up
+```
+(See [Docker Compose overview | Docker Docs](https://docs.docker.com/compose/)
+for more information on managing containes with `docker compose`.)
+
+
+### Initial setup
+
+Before the chooser-node container can be used effectively, a clean install of
+NPM packages from `package-lock.json` is required:
+```shell
+docker compose exec chooser-node npm ci
+```
+**This step generally only needs to be done once.**
+
+
 ### Run Node development server
 
-1. Perform a clean install of NPM packages from `package-lock.json`
-    ```shell
-    docker compose exec chooser-node npm ci
-    ```
-   - (this initial step can be skipped if previously completed)
-2. Run Node development server
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+3. Run Node development server
     ```shell
     docker compose exec chooser-node npm run serve
     ```
@@ -85,12 +102,9 @@ installation instructions.
 
 ### Create production (standalone) build
 
-1. Perform a clean install of NPM packages from `package-lock.json`
-    ```shell
-    docker compose exec chooser-node npm ci
-    ```
-   - (this initial step can be skipped if previously completed)
-2. Run Node development server
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+3. Run Node development server
     ```shell
     docker compose exec chooser-node npm run build
     ```
@@ -105,12 +119,9 @@ when making modifications to this location.
 
 ### Create standalone (production) build
 
-1. Perform a clean install of NPM packages from `package-lock.json`
-    ```shell
-    docker compose exec chooser-node npm ci
-    ```
-   - (this initial step can be skipped if previously completed)
-2. Run Node development server
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+3. Run Node development server
     ```shell
     docker compose exec chooser-node npm run build
     ```
@@ -131,12 +142,9 @@ docker compose exec chooser-node VUE_APP_CC_OUTPUT=embedded npm run build
 
 ### Create a web component build
 
-1. Perform a clean install of NPM packages from `package-lock.json`
-    ```shell
-    docker compose exec chooser-node npm ci
-    ```
-   - (this initial step can be skipped if previously completed)
-2. Run Node development server
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+3. Run Node development server
     ```shell
     docker compose exec chooser-node npm run build-component
     ```
@@ -165,19 +173,35 @@ docker compose exec chooser-node VUE_APP_CC_OUTPUT=embedded npm run build-compon
 ```
 
 
-## Running Tests
+## Perform unit tests on standalone or embedded build
 
-You can run tests by executing:
-```shell
-docker compose exec chooser-node npm run test
-```
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+2. Run unit tests
+    ```shell
+    docker compose exec chooser-node npm run test:unit
+    ```
 
-For running tests on a web-component build, run:
-```shell
-docker compose exec chooser-node npm run test-component
-```
+## Perform unit tests on web-component build
 
-It starts a server with the `dist/demo.html` on which tests can be run.
+1. Startup containers (see above)
+2. Complete initial setup (see above)
+3. Create a web component build (see above)
+2. Run unit tests
+    ```shell
+    docker compose exec chooser-node npm run test-component
+    ```
+   - It starts a server with the `dist/demo.html` on which tests can be run.
+
+
+## Perform Cypress tests
+
+1. Startup containers (see above)
+2. Run Cypress tests
+    ```shell
+    docker run -it -v $PWD:/e2e -w /e2e -e CYPRESS_baseUrl=http://host.docker.internal:8888 cypress/included:latest
+    ```
+   - (This will download the cypress/included image when first run) 
 
 
 ## CSS Build

docker-compose.yml

@@ -5,18 +5,23 @@ version: '2.4'
 services:
 
   chooser-web:
-    # https://hub.docker.com/_/nginx/
-    image: 'nginx:latest'
+    build: .
     ports:
       - '8888:80'
     restart: on-failure
     volumes:
-      - './docs:/usr/share/nginx/html:ro'
+      - '.:/app:ro'
 
   chooser-node:
     # continue running until shutdown (allows docker compose exec which is much
     # faster than docker compose run) per https://serverfault.com/a/1084975
     command: sh -c 'trap "exit" TERM; while true; do sleep 1; done'
+    environment:
+      # Store caches in repository directory. This save time across container
+      # runs. NOTE: cypress is not supported in this container--see README.md
+      CYPRESS_CACHE_FOLDER: /app/.cache/Cypress
+      npm_config_cache: /app/.npm
+      npm_config_devdir: /app/.cache/node-gyp
     image: 'node:14'
     ports:
       - '8080:8080'