Using pnpm start
in local Docker deployment causes issues with PostHog and Supabase
#59
Labels
pnpm start
in local Docker deployment causes issues with PostHog and Supabase
#59
Describe the bug
This is relevant to local prod deployments. When running
pnpm start
inside of Docker causes errors initializing Supabase and Posthog. Supabase looks for url and key, and posthog fails to initialize.To Reproduce
Steps to reproduce the behavior:
Overwrite the docker entrypoint command for frontend/Dockerfile (either in the dockerfile or in docker-compose.prod.yaml) to use
pnpm start
, and set NODE_ENV="production"Expected behavior
It should run normally and load the app
Additional context
Workaround is to just use
pnpm dev
, even though we're using a multi-stage build and actually building the nextjs project withpnpm run build
I have a draft PR that may help with the posthog issue: #58 , feel free to use this as a starting point.
The text was updated successfully, but these errors were encountered: