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
**@vercel/kv** redis is now optional for the dashboard. The app boots
and runs core auth + dashboard flows without `KV_REST_API_URL` /
`KV_REST_API_TOKEN` configured.
> **Note**: For production deployments, we use Vercel KV Storage integration, which provides a managed Redis-compatible store and automatically configures these environment variables. You can add this integration through the Vercel dashboard when deploying your project.
73
-
74
-
#### b. Supabase Setup
60
+
#### a. Supabase Setup
75
61
1. Create a new Supabase project
76
62
2. Go to Project Settings > API
77
63
3. Copy the `anon key` & `service_role key` to populate `.env.local`
@@ -97,10 +83,23 @@ This project requires a Redis-compatible key-value store. You'll need to:
2. Create a new **public** bucket named `profile-pictures`
103
89
90
+
#### c. Key-Value Store Setup (Optional)
91
+
Redis/KV is optional for standard dashboard deployments, including local, enterprise, and on-prem environments. The dashboard can boot and run core auth and dashboard workflows without KV configured.
92
+
93
+
KV is currently used for optional capability checks and for deduplicating ZeroBounce alternate-email warnings. If you need those capabilities, configure a Vercel/Upstash Redis REST-compatible store:
94
+
```
95
+
KV_REST_API_URL=your_redis_rest_api_url
96
+
KV_REST_API_TOKEN=your_redis_api_write_token
97
+
```
98
+
99
+
> **Note**: `@vercel/kv` expects a Redis REST API. A raw Redis server such as `redis://localhost:6379` is not compatible without an Upstash-compatible REST proxy.
100
+
101
+
> **Health check**: When `KV_REST_API_URL` and `KV_REST_API_TOKEN` are set, `/api/health` will report `503 degraded` if KV is unreachable. Leave both unset to opt out of the KV health check entirely.
0 commit comments