fixing docker deployment#220
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4545e75aa0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| NEXT_PUBLIC_UPLOADTHING_ENABLED: ${NEXT_PUBLIC_UPLOADTHING_ENABLED:-} | ||
| # Inngest — required in production for background job processing | ||
| INNGEST_EVENT_KEY: ${INNGEST_EVENT_KEY} | ||
| INNGEST_EVENT_KEY: ${INNGEST_EVENT_KEY:-placeholder} |
There was a problem hiding this comment.
Using INNGEST_EVENT_KEY: ${INNGEST_EVENT_KEY:-placeholder} allows the app to start even when no real key is configured, but src/env.ts only validates that the value is non-empty and InngestDispatcher will still try to dispatch jobs with that bogus key; in production-like deployments this turns a clear startup misconfiguration into runtime job-delivery failures (401/failed sends) after users trigger background processing.
Useful? React with 👍 / 👎.
1 participant
No description provided.