Core workflow

Static previews

Publish a static directory to an isolated, expiring preview origin.

Before you start

Build the static site locally with index.html at the directory root.
Select the workspace and project that should own the preview files.

Publish a preview

isolated static preview

blobyard preview ./preview-site --expires 24h

The command uses the scope stored by blobyard init, or explicit --workspace and --project flags.
The directory must contain index.html at its root.
A preview holds up to 10,000 files resolved from an immutable manifest.
Without --expires a preview lasts seven days, and the longest allowed lifetime is thirty days.

Trust the isolation boundary

Each preview is served from its own capability subdomain under blobyard.dev. Preview HTML never runs on the authenticated application origin and cannot receive application cookies.

Manage previews from the project page in the dashboard, or list and revoke them through the API and MCP tools. Revoking a preview stops the origin from resolving while the uploaded files remain in the project.

Reference and troubleshooting

Syntax and behavior

Reusable syntax

preview syntax

blobyard preview <local-directory> [--expires <duration>]

Concrete example

one-day preview

blobyard --workspace demo-team --project release-files preview ./preview-site --expires 24h

Values used

./preview-site: Local static directory containing index.html.
24h: Preview lifetime of one day. The maximum lifetime is thirty days.

Expected result

The command uploads the directory and returns one isolated preview URL on a blobyard.dev capability subdomain.

If it fails

Add index.html at the preview directory root if validation fails.
Split very large sites. A preview resolves at most 10,000 files.

Security and lifecycle

Preview HTML runs on an isolated origin that cannot receive application cookies. The URL is a capability, so share it deliberately.