You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/examples/vercel-sync-env-vars.mdx
+11-46Lines changed: 11 additions & 46 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Syncing environment variables from your Vercel projects"
3
-
sidebarTitle: "Syncing Vercel env vars"
3
+
sidebarTitle: "Vercel sync environment variables"
4
4
description: "This example demonstrates how to sync environment variables from your Vercel project to Trigger.dev."
5
5
---
6
6
@@ -12,60 +12,25 @@ This example shows how to automatically sync environment variables from your Ver
12
12
13
13
## Build configuration
14
14
15
-
To sync environment variables from your Vercel project to Trigger.dev, you'll first need to add this build configuration to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your project.
15
+
To sync environment variables from your Vercel project to Trigger.dev, you just need to add this build configuration to your `trigger.config.ts` file. This extension will then automatically run every time you deploy your project.
16
16
17
17
This code syncs encrypted environment variables, filtering them based on the current environment (production, preview, or development).
18
18
19
+
<Note>
20
+
You need to set the `VERCEL_ACCESS_TOKEN` and `VERCEL_PROJECT_ID` environment variables, or pass
21
+
in the token and project ID as arguments to the `vercelSyncEnvVars` build extension.
0 commit comments