NEXT_PUBLIC_NAME
and value YOUR_NAME
.
NEXT_PUBLIC_NAME
and value ANOTHER_NAME
.
create-next-app
to initialize an app called infisical-nextjs
.
pages/_app.js
, lets add a console.log()
to print out the environment variable in the browser console.
init
command at the root of the Next.js app. This step connects your local project to the project on the Infisical platform and creates a infisical.json
file containing a reference to that latter project.
dev
; you can inject secrets from different
environments by modifying the env
flag as per the CLI documentation.
At this stage, you know how to use the Infisical CLI to inject secrets into your Next.js app for local development.
AWS_SECRET_KEY
, AWS_EXECUTION_ENV
, AWS_LAMBDA_LOG_GROUP_NAME
,
AWS_LAMBDA_LOG_STREAM_NAME
, AWS_LAMBDA_FUNCTION_NAME
,
AWS_LAMBDA_FUNCTION_MEMORY_SIZE
, AWS_LAMBDA_FUNCTION_VERSION
,
NOW_REGION
, TZ
, LAMBDA_TASK_ROOT
, LAMBDA_RUNTIME_DIR
,
AWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY
, AWS_SESSION_TOKEN
,
AWS_REGION
, and AWS_DEFAULT_REGION
.Why should I use Infisical if I can centralize all my Next.js + Vercel environment variables across all environments directly in Vercel?
Is opting out of end-to-end encryption for the Infisical-Vercel integration safe?