Cache Priming

This project updates launch.json before builds to prime the cache with up to 50 content URLs (Launch's limit per deployment) that are marked for sitemap inclusion. The list is generated from Contentstack entries and written to the cache.cachePriming.urls array.

How It Works

• The updateLaunchConfig.mjs script queries Contentstack for page, blogpost, guide, kickstart, live_stream, and person entries.
• Only entries with metadata.include_in_sitemap === true are included.
• URLs are picked in priority order until the 50-URL cap (MAX_PRIMED_URLS) is reached: / and /index.md, pages, guide overviews, kickstarts, blog posts (newest date first), then guide chapters, live streams and person pages.
• The final list is sorted alphabetically so diffs stay stable.
• /index.md is always included so homepage markdown is primed separately from HTML /. Accept negotiation at the Launch edge rewrites markdown / to /index.md before the cache lookup, so the primed HTML object is not reused.
• Existing launch.json settings are preserved; only cache.cachePriming.urls is overwritten.

When It Runs

The script runs automatically during npm run build via the prebuild hook:

npm run prebuild

Required Environment Variables

The script is skipped if any required values are missing:

• NEXT_PUBLIC_CONTENTSTACK_API_KEY
• NEXT_PUBLIC_CONTENTSTACK_DELIVERY_TOKEN
• NEXT_PUBLIC_CONTENTSTACK_ENVIRONMENT

The script loads .env files using @next/env, so the same environment file setup that works for next build will be picked up here. If the required values are still unset, the build continues and launch.json is not modified.