Work-around for npm perm error in CI/CD system

Started hitting this issue npm/uid-number#3.
Seems to be related to how this different CI system is building the
container. Docs for this option can be found:
https://docs.npmjs.com/misc/config.

I don't see any security risks here since we are docker multi-container
building and yanking out files from the initial node build.

docker/1-prod-node

@@ -9,7 +9,7 @@ RUN apk add --no-cache paxctl python make g++
 RUN paxctl -cm /usr/local/bin/node
 
 # Install gulp globally so it can be used during builds
-RUN npm install --global gulp-cli
+RUN NPM_CONFIG_UNSAFE_PERM=true npm install --global gulp-cli
 
 COPY ./ /src-files
 RUN cd /src-files && ( npm install && gulp build:production )

docker/ProdDjangoDockerfile

@@ -9,7 +9,7 @@ RUN apk add --no-cache paxctl python make g++
 RUN paxctl -cm /usr/local/bin/node
 
 # Install gulp globally so it can be used during builds
-RUN npm install --global gulp-cli
+RUN NPM_CONFIG_UNSAFE_PERM=true npm install --global gulp-cli
 
 COPY ./ /src-files
 RUN cd /src-files && ( npm install && gulp build:production )