Fixed process.env.NEXT_PUBLIC_... not loaded after docker build #420
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important
Replaced direct
process.env.NEXT_PUBLIC_...
access withgetPublicEnvVar()
across the codebase and updated Docker entrypoint for environment variable handling.getPublicEnvVar()
inenv.tsx
to access environment variables, replacing directprocess.env.NEXT_PUBLIC_...
access.sentry.client.config.ts
,providers.tsx
,layout.tsx
, and 8 other files to usegetPublicEnvVar()
..eslintrc.cjs
to restrict direct access toprocess.env.NEXT_PUBLIC_*
.entrypoint.sh
to replace environment variable sentinels in the dashboard build output.This description was created by for a98bcb8. It will automatically update as commits are pushed.