Dan
aca2f54cb7
* Added sync env vars docs example * Added links in the config + deploy files * Updated copy * Added vercel docs cards and added them to all of the relevant docs pages * Added sync env vars to the intro page * Added automatically sync env vars section to nextjs guide * Added ‘Manually’ * Removed code block and updated title * updated formatting and added vercelsyncenvvars to the config file * Added missing comment * Updated imports to /core * Added sync env var docs link and note * Improved the VERCEL_ACCESS_TOKEN note * Added link to vercel * Updated docs and improved formatting * Copy tweaks * Added space * Updated deploy docs
12 lines
749 B
Plaintext
12 lines
749 B
Plaintext
## Manually add your environment variables (optional)
|
|
|
|
If you have any environment variables in your tasks, be sure to add them in the dashboard so deployed code runs successfully. In Node.js, these environment variables are accessed in your code using `process.env.MY_ENV_VAR`.
|
|
|
|
In the sidebar select the "Environment Variables" page, then press the "New environment variable"
|
|
button. 
|
|
|
|
You can add values for your local dev environment, staging and prod. 
|
|
|
|
You can also add environment variables in code by following the steps on the [Environment Variables page](/deploy-environment-variables#in-your-code).
|