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.
This commit is contained in:
@@ -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":"<entry id>"}` |
|
||||
| Menu-entry reorder | `{"kind":"menu_entry","slug":"partition:<menu id>"}` (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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user