Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using pnpm start in local Docker deployment causes issues with PostHog and Supabase #59

Closed
daryllimyt opened this issue Apr 18, 2024 · 1 comment
Labels
bug Something isn't working build good first issue Good for newcomers

Comments

@daryllimyt
Copy link
Contributor

daryllimyt commented Apr 18, 2024

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 with pnpm run build

I have a draft PR that may help with the posthog issue: #58 , feel free to use this as a starting point.

@daryllimyt daryllimyt added bug Something isn't working good first issue Good for newcomers build labels Apr 18, 2024
@daryllimyt
Copy link
Contributor Author

Supabase no longer relevant, open up in the future if posthog issues persist

@daryllimyt daryllimyt closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working build good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant