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
> **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.
79
-
80
-
#### b. Supabase Setup
66
+
#### a. Supabase Setup
81
67
1. Create a new Supabase project
82
68
2. Go to Project Settings > API
83
69
3. Copy the `anon key` & `service_role key` to populate `.env.local`
@@ -103,18 +89,33 @@ This project requires a Redis-compatible key-value store. You'll need to:
- Navigate to the `/migrations` folder in the project
109
95
- Execute each SQL migration file in sequential order against your Supabase database
110
96
- You can run these migrations using the Supabase SQL Editor or a PostgreSQL client
111
97
- Make sure to apply migrations in the correct order based on their timestamp prefixes
112
98
113
-
#### d. Supabase Storage Setup
99
+
#### c. Supabase Storage Setup
114
100
1. Go to Storage > Buckets
115
101
2. Create a new **public** bucket named `profile-pictures`
116
102
117
-
#### e. Start the development server
103
+
5. Optional services:
104
+
105
+
#### a. Key-Value Store Setup
106
+
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.
107
+
108
+
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:
109
+
```
110
+
KV_REST_API_URL=your_redis_rest_api_url
111
+
KV_REST_API_TOKEN=your_redis_api_write_token
112
+
```
113
+
114
+
> **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.
115
+
116
+
> **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