🐛 fix(docker): write .env file for Vite during production build#71
Merged
656d696c65 merged 2 commits intomainfrom Mar 12, 2026
Merged
🐛 fix(docker): write .env file for Vite during production build#71656d696c65 merged 2 commits intomainfrom
656d696c65 merged 2 commits intomainfrom
Conversation
Vite reads VITE_* variables from .env files, not from process.env. The production Dockerfile was setting them via ENV directives, which had no effect on import.meta.env in the built output. - Move ARG declarations into the build stage where they are used - Write VITE_* build args to packages/website/.env before building - Remove unused ENV directives for Vite variables - Pass VITE_API_BASE_URL and VITE_WEBSITE_BASE_URL from GitHub Actions variables into the publish workflow build step
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Vite reads VITE_* variables from .env files, not from process.env. The production Dockerfile was setting them via ENV directives, which had no effect on import.meta.env in the built output.