From b26e5ff6ab46e1baa27af9ccd1f6a85899af7729 Mon Sep 17 00:00:00 2001 From: Nathan Flurry Date: Sun, 28 Jun 2026 22:10:43 -0700 Subject: [PATCH] fix(docker): don't leak FA Pro token into build logs The ARG is already in the RUN environment, so the icons generate reads FONTAWESOME_PACKAGE_TOKEN directly instead of exporting it (which printed the token into Railway build logs). Build behaviour unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) --- website/Dockerfile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/Dockerfile b/website/Dockerfile index 1e7d4b55..cc4b7733 100644 --- a/website/Dockerfile +++ b/website/Dockerfile @@ -14,8 +14,9 @@ RUN apk add --no-cache git && npm install -g pnpm@9 # in this discarded build stage — the final caddy image never contains it. ARG DOCS_THEME_SHA=450c498555135098c6a927adfdf13458be9be22a ARG FONTAWESOME_PACKAGE_TOKEN -RUN export FONTAWESOME_PACKAGE_TOKEN="$FONTAWESOME_PACKAGE_TOKEN" \ - && git clone https://github.com/rivet-dev/docs-theme.git /theme \ +# The ARG is already in this RUN's environment, so the icons generate reads +# FONTAWESOME_PACKAGE_TOKEN directly — we don't echo it into the build log. +RUN git clone https://github.com/rivet-dev/docs-theme.git /theme \ && git -C /theme checkout "$DOCS_THEME_SHA" \ && pnpm -C /theme install \ && pnpm -C /theme/packages/theme/vendor/icons run gen:manifest \