@@ -16,37 +16,38 @@ declare global {
1616 WORKER_SELF_REFERENCE ?: Service ;
1717
1818 // KV used for the incremental cache
19- NEXT_CACHE_KV ?: KVNamespace ;
19+ NEXT_INC_CACHE_KV ?: KVNamespace ;
2020
2121 // R2 bucket used for the incremental cache
22- NEXT_CACHE_R2_BUCKET ?: R2Bucket ;
22+ NEXT_INC_CACHE_R2_BUCKET ?: R2Bucket ;
2323 // Prefix used for the R2 incremental cache bucket
24- NEXT_CACHE_R2_PREFIX ?: string ;
24+ NEXT_INC_CACHE_R2_PREFIX ?: string ;
2525
2626 // D1 db used for the tag cache
27- NEXT_CACHE_D1 ?: D1Database ;
27+ NEXT_TAG_CACHE_D1 ?: D1Database ;
2828
29- // Durable Object namespace to use for the durable object queue handler
30- NEXT_CACHE_DO_REVALIDATION ?: DurableObjectNamespace < DurableObjectQueueHandler > ;
3129 // Durables object namespace to use for the sharded tag cache
32- NEXT_CACHE_DO_SHARDED ?: DurableObjectNamespace < DOShardedTagCache > ;
30+ NEXT_TAG_CACHE_DO_SHARDED ?: DurableObjectNamespace < DOShardedTagCache > ;
3331 // Queue of failed tag write
3432 // Optional, could be used to monitor or reprocess failed writes
35- NEXT_CACHE_DO_SHARDED_DLQ ?: Queue ;
33+ NEXT_TAG_CACHE_DO_SHARDED_DLQ ?: Queue ;
3634
37- // Below are the potential environment variables that can be set by the user to configure the durable object queue handler
35+ // Durable Object namespace to use for the durable object queue
36+ NEXT_CACHE_DO_QUEUE ?: DurableObjectNamespace < DurableObjectQueueHandler > ;
37+
38+ // Below are the environment variables to configure the durable object queue
3839 // The max number of revalidations that can be processed by the durable worker at the same time
39- MAX_REVALIDATION_BY_DURABLE_OBJECT ?: string ;
40+ NEXT_CACHE_DO_QUEUE_MAX_REVALIDATION ?: string ;
4041 // The max time in milliseconds that a revalidation can take before being considered as failed
41- REVALIDATION_TIMEOUT_MS ?: string ;
42+ NEXT_CACHE_DO_QUEUE_REVALIDATION_TIMEOUT_MS ?: string ;
4243 // The amount of time after which a revalidation will be attempted again if it failed
4344 // If it fails again it will exponentially back off until it reaches the max retry interval
44- REVALIDATION_RETRY_INTERVAL_MS ?: string ;
45+ NEXT_CACHE_DO_QUEUE_RETRY_INTERVAL_MS ?: string ;
4546 // The maximum number of attempts that can be made to revalidate a path
46- MAX_REVALIDATION_ATTEMPTS ?: string ;
47+ NEXT_CACHE_DO_QUEUE_MAX_NUM_REVALIDATIONS ?: string ;
4748 // Disable SQLite for the durable object queue handler
4849 // This can be safely used if you don't use an eventually consistent incremental cache (i.e. R2 without the regional cache for example)
49- REVALIDATION_DO_DISABLE_SQLITE ?: string ;
50+ NEXT_CACHE_DO_QUEUE_DISABLE_SQLITE ?: string ;
5051 }
5152}
5253
0 commit comments