cloud: force-dynamic layout so GTM_ID env is read at runtime#271
Merged
Conversation
Without this, Next.js statically prerenders the layout during `next build` and bakes in whatever GTM_ID was set in CI (empty). The cloud droplet's runtime env never gets a chance to set it, so the GTM script never renders. Forcing dynamic rendering keeps a single Docker image usable for both flavors: GTM_ID on the cloud droplet activates the banner, self-hosted containers leave it unset and ship nothing. Tradeoff: static optimization is lost for /, /login, /forgot-password, etc. Acceptable for an admin app — most pages already SSR per request.
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.
Follow-up to #269. Without
export const dynamic = 'force-dynamic'Next.js statically prerendered the layout in CI (where GTM_ID is empty), so the GTM script never appeared in the served HTML on the cloud droplet despite the runtime env being set. Forcing dynamic rendering keeps the single-image goal intact: the droplet's env activates GTM, self-hosted leaves it empty.