walrus-sites-publishing

Publish and update Walrus Sites static frontends with site-builder CLI.

10|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MystenLabs/skills --skill walrus-sites-publishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walrus-sites-publishing
Source: https://github.com/MystenLabs/skills/tree/main/walrus-sites/publishing
Command: npx skills add https://github.com/MystenLabs/skills --skill walrus-sites-publishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you publish, update, and troubleshoot decentralized static websites on Walrus Sites, including preventing outages caused by blob expiration and fixing SPA routing issues.

Core Features & Use Cases

  • Publish new Walrus Sites deployments with the site-builder publish command, including selecting safe --epochs lifetimes.
  • Update existing sites in place with site-builder update and update-resources, preserving the same site object and avoiding new URLs.
  • Manage critical configuration and lifecycle details such as ws-resources.json, SPA route fallback via routes, custom caching headers via headers, and diagnosing failures using site-builder sitemap expiration dates.
  • Administer site operations including destroying a site and extending blob storage before expiry.

Quick Start

Use the Walrus Sites publishing workflow by building your frontend and then running site-builder publish --epochs 30 dist/ for a testnet deployment.

Frequently Asked Questions about walrus-sites-publishing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a static website to Walrus Sites from a dist directory?

To deploy a static website to Walrus Sites, you use the site-builder CLI to convert your built dist/ directory into a resolvable on-chain site object, typically running `site-builder publish --epochs 30 dist/` for a testnet deployment.

How can I update an existing Walrus Site in place without generating a new URL?

You can update an existing Walrus Site in place by using the `site-builder update` and `update-resources` commands, which preserves the same on-chain site object and avoids generating new URLs for your static frontend.

How do I configure SPA routing fallback for a decentralized static website on Walrus?

Configuring SPA routing for a Walrus Site requires setting up route fallbacks within the ws-resources.json file, ensuring client-side routing requests are correctly resolved by the decentralized static website host.

Why do my Walrus Sites blobs expire and how can I extend their storage lifetime?

Walrus Site blobs expire because they are assigned a specific epoch lifetime during publication; you can diagnose expiration dates using `site-builder sitemap` and extend blob storage before expiry to prevent outages.

What prerequisites are needed to publish and manage Walrus Sites static frontends?

Publishing Walrus Sites static frontends requires the site-builder and walrus CLIs, a configured Sui environment, sufficient gas and WAL funds, and correct dist/ build artifacts to successfully turn the directory into an on-chain object.

Can I set custom caching headers for static assets deployed on Walrus Sites?

Yes, you can set custom caching headers for static assets deployed on Walrus Sites by defining the desired header configurations inside your ws-resources.json file during the site publishing or update workflow.