feat: set NODE_ENV variable for production in Dockerfiles and update dotenv config for environment file selection

Author: mitchdowney

Dockerfile.build.alpha

@@ -12,6 +12,8 @@ RUN npm install podverse-helpers@alpha
 
 # Stage 2: Build the app
 FROM deps AS builder
+# required for pre-build scripts to use. within next.js app, NODE_ENV is controlled by next.js
+ENV NODE_ENV=production
 COPY . .
 
 # Ensure the source env file actually exists! 

Dockerfile.build.local

@@ -12,6 +12,8 @@ RUN npm install podverse-helpers@alpha
 
 # Stage 2: Build the app
 FROM deps AS builder
+# required for pre-build scripts to use. within next.js app, NODE_ENV is controlled by next.js
+ENV NODE_ENV=production
 COPY . .
 
 # Ensure the source env file actually exists! 

scripts/build/external-services/firebase/generate-firebase-sw.js

@@ -6,8 +6,10 @@
 const fs = require('fs');
 const path = require('path');
 
+// Choose .env file: use .env.production when running in production
+const envFileName = process.env.NODE_ENV === 'production' ? '.env.production' : '.env';
 // Load .env file from project root
-require('dotenv').config({ path: path.join(__dirname, '..', '..', '..', '..', '.env') });
+require('dotenv').config({ path: path.join(__dirname, '..', '..', '..', '..', envFileName) });
 
 const outPath = path.join(__dirname, '..', '..', '..', '..', 'public', 'firebase-messaging-sw.js');
 const templatePath = path.join(__dirname, 'firebase-messaging-sw.template.js');