fix: ensure db-init-prod service builds correctly in Docker production (#48)

- Add db-init-prod to docker-build-prod.sh build targets to fix "wait-for-postgres.sh: not found" error
- Reduce memory limit from 20g to 10g to support builds on 16GB RAM systems
- Make generate-version.js resilient to Docker build environments by wrapping file writes in try/catch blocks
- This ensures db-init-prod service has access to wait-for-postgres.sh script during startup

Author: therealbrad

testplanit/docker-build-prod.sh

@@ -6,9 +6,7 @@ export DOCKER_BUILDKIT=1
 
 # Build with explicit memory limits
 docker compose -f docker-compose.prod.yml build \
-  --memory 20g \
-  --memory-swap 24g \
-  --cpus 2 \
-  prod workers
+  --memory 10g \
+  prod workers db-init-prod
 
 echo "Build complete!"

testplanit/scripts/generate-version.js

@@ -72,16 +72,24 @@ if (environment === 'development') {
 }
 
 const envPath = path.join(__dirname, '..', envFileName);
-fs.writeFileSync(envPath, envContent);
+try {
+  fs.writeFileSync(envPath, envContent);
+} catch (error) {
+  console.warn(`Could not write to ${envFileName}, skipping (this is normal in Docker builds):`, error.message);
+}
 
 // Also write a version.json file for reference
 const versionJsonPath = path.join(__dirname, '..', 'public', 'version.json');
 // Ensure public directory exists
 const publicDir = path.join(__dirname, '..', 'public');
-if (!fs.existsSync(publicDir)) {
-  fs.mkdirSync(publicDir, { recursive: true });
+try {
+  if (!fs.existsSync(publicDir)) {
+    fs.mkdirSync(publicDir, { recursive: true });
+  }
+  fs.writeFileSync(versionJsonPath, JSON.stringify(versionInfo, null, 2));
+} catch (error) {
+  console.warn(`Could not write version.json, skipping (this is normal in Docker builds):`, error.message);
 }
-fs.writeFileSync(versionJsonPath, JSON.stringify(versionInfo, null, 2));
 
 console.log('Version information generated:');
 console.log(`  Version: ${version}`);