ES
GitHub
Documentation

DOC / 16 / DELIVERY

Build and deploy

Verify the output ledger, preview production bytes, select release artifacts, and deploy static output.

In this guideBuild and deploy
Getting startedProject structureCLI referenceDeveloper loopRouting and pagesRust viewsEvents and foldsSchemas and snapshotsHyphae verified syncTyped contentBrowser runtimeDOM ownershipAdaptive assetsArtifact trustErrors and diagnosticsBuild and deployCrates and APILicensing and policy

Build production bytes

shell
pliego check
pliego build
pliego inspect
pliego preview 4400

build compiles the optional WASM client in release mode, runs wasm-bindgen, executes the native site package, stages output atomically, and verifies the emitted ledger. preview refuses output that cannot prove its file list.

Inspect the artifact

pliego.build.json is the ownership boundary between source and deployment. It binds route files, assets, hashes, source revision, toolchain identity, and the output contract consumed by inspect, preview, and release workflows.

Release selection

GitHub Releases is the canonical distribution channel. Production targets are Linux x86_64 and ARM64; macOS and Windows artifacts support development. Versioned archives, sidecars, SHA256SUMS, and the signed release manifest must agree.

shell
# Run only after downloading the installer to disk
./install.sh --version 0.0.1

# Explicit mutable-channel opt-in
./install.sh --channel latest

Deploy the static output

Deploy the contents of target/site to any origin that preserves paths, MIME types, immutable asset caching, the authored 404 document, and clean-route fallback. The framework does not require a PliegoRS application server.