.env

# See https://nextjs.org/docs/basic-features/environment-variables

# XXX Tips: How is this file meant to be used?
# This file is tracked by git and must only contains NON-SENSITIVE information, which is usually meant to be available in the browser.
# Sensitive information (server-side only) MUST be written in ".env.local" file instead (which isn't tracked by git).

# XXX Tips: When is this file being used?
# This file is used only when building the Next.js app locally (localhost), whether it's for running `next dev` or `next build`.
# For staging/production stages, the app relies on "vercel.{NEXT_PUBLIC_CUSTOMER_REF}.{NEXT_PUBLIC_APP_STAGE}.yml:build.env".

# XXX Tips: What's the difference between env vars starting with "NEXT_PUBLIC_" and the others?
# All env variables that DON'T start with "NEXT_PUBLIC_" MUST be manually exposed by ./next.config.js for the project to work locally
# "NEXT_PUBLIC_" has a semantic purpose. If you mean to use a variable on the browser, then you should use "NEXT_PUBLIC_".
# Any non-sensitive env variable should start with "NEXT_PUBLIC_".
# Sensitive information MUST NOT start with "NEXT_PUBLIC_".
# You must be careful to use sensitive information only on the server-side, because if you use them on the browser or getInitialProps, they'll be leaked, even if the variable doesn't start with "NEXT_PUBLIC_".
# Any change to this file needs a server restart to be applied.

# The stage is "how" the application is running.
# It can be either "development", "staging" or "production".
# This value is also set in each "vercel.*.json" files, so that other stages use their own value.
# Tip: This value must not be changed.
# Tip: You may override it from ".env.local" if you want to simulate another stage, locally.
NEXT_PUBLIC_APP_STAGE=development

# The name of the NRN preset being used.
# Used by the demo to redirect to the preset branch/documentation.
NEXT_PUBLIC_NRN_PRESET=v2-mst-aptd-at-lcz-sty

# The customer that is being used.
# Tip: You may override it from ".env.local" if you want to simulate another customer, locally.
NEXT_PUBLIC_CUSTOMER_REF=customer1

# Locize project ID, can be found in the project "settings" page
# Used to fetch the i18n translations
# Tip: The value being used below is valid, so that you can run the demo locally without having to create your own Locize account, but you cannot make any change
NEXT_PUBLIC_LOCIZE_PROJECT_ID=658fc999-dfa8-4307-b9d7-b4870ad5b968

# Amplitude API key, can be found under "Manage Data > Project name > Project settings > API Key"
# Used to send analytics usage
# Tip: The value being used below is valid, so that you can run the demo locally without having to create your own Amplitude account, but you cannot access the data
NEXT_PUBLIC_AMPLITUDE_API_KEY=5ea02d86a6840c165fcc01377131fa13