Skip to content

fix(web): declare the Privacy/Terms build args in web/Dockerfile - #1053

Merged
jiashuoz merged 1 commit into
mainfrom
fix/web-dockerfile-legal-args
Sep 27, 2026
Merged

jiashuoz merged 1 commit into
mainfrom
fix/web-dockerfile-legal-args

Conversation

@jiashuoz

Copy link
Copy Markdown
Member

#1051 added NEXT_PUBLIC_PRIVACY_URL / NEXT_PUBLIC_TERMS_URL to web/src/lib/site.ts but not to web/Dockerfile, whose explicit ARG/ENV list is what lets a NEXT_PUBLIC_* value reach next build. docker build only warns about an unconsumed --build-arg, so the hosted 1.12.0 image built green with the links absent.

This adds the two declarations (empty defaults, so the published OSS image stays generic) and a comment stating the rule: every NEXT_PUBLIC_* read in site.ts must be declared here.

Verified locally that every process.env.NEXT_PUBLIC_* referenced by site.ts now has an ARG line.

🤖 Generated with Claude Code

#1051 read NEXT_PUBLIC_PRIVACY_URL and NEXT_PUBLIC_TERMS_URL in site.ts
but never declared them in web/Dockerfile, so `docker build` dropped the
hosted deployment's values and 1.12.0 shipped without the footer links or
the consent line. Adds the ARG/ENV pair and a comment explaining why the
Dockerfile is the allowlist.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@jiashuoz
jiashuoz merged commit 5eff1d1 into main Sep 27, 2026
29 checks passed
@jiashuoz
jiashuoz deleted the fix/web-dockerfile-legal-args branch September 27, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant