Fix: Magic link login not working properly when booted from docker (triggerdotdev#390)

arika0093 · web-flow · commit 5c1e00223351 · 2023-09-08T11:06:06.000+01:00
* fix: use NODE_ENV when starting from docker image When starting from `pnpm run start`, NODE_ENV is fixed to production, causing problems like triggerdotdev#186. So, I added `start_docker`, a process dedicated to docker, and started from it. The process is exactly the same as `start` except that NODE_ENV is not overwritten. * fix: align execution name with others * Change: command name to match review
diff --git a/apps/webapp/package.json b/apps/webapp/package.json
@@ -12,6 +12,7 @@
     "format": "prettier --write .",
     "lint": "eslint --cache --cache-location ./node_modules/.cache/eslint .",
     "start": "cross-env NODE_ENV=production node --max-old-space-size=8192 ./build/server.js",
+    "start:local": "cross-env node --max-old-space-size=8192 ./build/server.js",
     "typecheck": "tsc --noEmit",
     "db:seed": "node prisma/seed.js",
     "db:seed:local": "ts-node prisma/seed.ts",
diff --git a/docker/scripts/entrypoint.sh b/docker/scripts/entrypoint.sh
@@ -14,4 +14,4 @@ cp node_modules/@prisma/engines/*.node apps/webapp/prisma/
 pnpm --filter webapp db:seed
 
 cd /triggerdotdev/apps/webapp
-exec dumb-init pnpm run start
+exec dumb-init pnpm run start:local
