ALGOFLOW Docs

Deploying Static dApps

Structure static dApp projects for predictable builds, easy IPFS publishing, and reproducible releases.

Last updated: 2026-03-22

Recommended Project Structure

Keep output deterministic so every deployment can be traced by commit + CID.

Exampletext
my-dapp/
  index.html
  app.js
  styles.css
  assets/
    logo.svg

Deployment Inputs

  • •Label/domain key for project identity.
  • •Build command and output directory for generated assets.
  • •Optional environment variables for compile-time config.
  • •Root directory when deploying from a monorepo.

Release Versioning

Each deployment produces a new CID and appears in deployment history.

Use notes and commit references in metadata for quick rollback analysis.

Tip: Pin production builds in two places (primary pinning provider + backup node) for stronger availability.