From 128a33d1e7453eb1ad0e9acdae324a9cecac3ab2 Mon Sep 17 00:00:00 2001 From: Jakub Zych Date: Fri, 6 Nov 2026 10:12:13 +0100 Subject: [PATCH] docs: the site's purge token is NUXT_CACHE_PURGE_TOKEN The layers renamed it from NUXT_SITE_CACHE_PURGE_TOKEN, which nuxt-site-config published in every page's payload. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8eca3e7..47e54d2 100644 --- a/README.md +++ b/README.md @@ -143,7 +143,7 @@ Every committed admin write of the menu screens sends one purge request to the h | Menu-entry create, update, delete | `{"kind":"menu_entry","slug":""}` | | Menu-entry reorder | `{"kind":"menu_entry","slug":"partition:"}` (through cabana's `pact.ReorderAfterSave` hook) | -Configure it once for the application with the framework keys `site_cache.purge_url` and `site_cache.purge_token` (`SUMMER_SITE_CACHE__PURGE_URL`, `SUMMER_SITE_CACHE__PURGE_TOKEN`); a site that extends `vue-menu-layer` 0.2.0 or later serves the matching route `POST /api/__site__/cache/purge` with `NUXT_SITE_CACHE_PURGE_TOKEN`. Without the keys nothing is sent. The entry checks (menu, parent, type, URL, target) run first: a refused save sends nothing, and a failing or slow site never fails a save or a reorder. +Configure it once for the application with the framework keys `site_cache.purge_url` and `site_cache.purge_token` (`SUMMER_SITE_CACHE__PURGE_URL`, `SUMMER_SITE_CACHE__PURGE_TOKEN`); a site that extends `vue-menu-layer` 0.2.0 or later serves the matching route `POST /api/__site__/cache/purge` with `NUXT_CACHE_PURGE_TOKEN` (`vue-menu-layer` 0.4.0 or later; earlier layers read `NUXT_SITE_CACHE_PURGE_TOKEN`, which nuxt-site-config publishes in every page's payload). Without the keys nothing is sent. The entry checks (menu, parent, type, URL, target) run first: a refused save sends nothing, and a failing or slow site never fails a save or a reorder. ### Winter import