sfnext-deployment
Build and deploy a Storefront Next storefront: pnpm build, pnpm push / sfnext push to Managed Runtime (MRT), MRT credentials (MRT_API_KEY, MRT_PROJECT, MRT_TARGET), syncing env vars with pnpm config:push-env, deploying the base cartridge and Page Designer metadata (pnpm cartridge:generate|validate|deploy), the shipped GitHub Actions deploy workflow, bundle size checks, the pre-launch checklist, and upgrading a project (template vs SDK compatibility, react-router pin). Use when a push fails or is rejected, a deployed site returns 500 or shows stale Page Designer components, "deploy to staging/production", or before go-live. Do not use for generic MRT project/environment/redirect/member management or log tailing (use b2c-cli:b2c-mrt), for config.server.ts and PUBLIC__ variable rules (use storefront-next:sfnext-configuration), or for creating the project (use storefront-next:sfnext-project-setup).
Pinned to revision fe78868e0e70, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/sfnext-deployment/SKILL.md
- skills/sfnext-deployment/evals/trigger-evals.json
- skills/sfnext-deployment/references/MRT-DEPLOYMENT.md
Every link opens the file at its source, pinned to the revision this page describes.