From 3b61c97fb32439f0ed0b5f6ff63f7e8418f83e85 Mon Sep 17 00:00:00 2001 From: Tim Date: Tue, 18 Mar 2025 20:52:35 -0500 Subject: [PATCH] add more information around what `NEXT_CACHE_REVALIDATION_WORKER` is --- pages/cloudflare/caching.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/cloudflare/caching.mdx b/pages/cloudflare/caching.mdx index e8adb01..1a6c469 100644 --- a/pages/cloudflare/caching.mdx +++ b/pages/cloudflare/caching.mdx @@ -32,7 +32,7 @@ npx wrangler@latest kv namespace create ##### 2. Add the KV namespace and Service Binding to your Worker -The binding name used in your app's worker is `NEXT_CACHE_WORKERS_KV`. +The binding name used in your app's worker is `NEXT_CACHE_WORKERS_KV`. The service binding should be a self reference to your worker where `` is the name in your wrangler configuration file. ```jsonc // wrangler.jsonc @@ -93,7 +93,7 @@ To use on-demand revalidation, you should also follow the [ISR setup steps](#inc ##### 1. Create a D1 database and Service Binding -The binding name used in your app's worker is `NEXT_CACHE_D1`. +The binding name used in your app's worker is `NEXT_CACHE_D1`. The service binding should be a self reference to your worker where `` is the name in your wrangler configuration file. ```jsonc // wrangler.jsonc