[Next.js][RAV][node-headless-ssr] Add Sitecore prefix to SITE_NAME environment variable and config #1672
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.
Description / Motivation
This is a follow-up to #1640 and #1647 which adds a Sitecore prefix to the new
SITE_NAME
environment variable and corresponding JSS config (so,SITECORE_SITE_NAME
andconfig.sitecoreSiteName
). This allows us to avoid environment variable name conflicts on deployment platforms (e.g.SITE_NAME
is a reserved env variable on Netlify).Also, re-introduces
SITECORE_JSS_APP_NAME
to the node-headless-ssr templates as this is still necessary (used differently than site name) in these apps.Testing Details
Types of changes