Skip to main content

​
Before you deploy

  • Deployments run from the main branch. Make sure main includes your latest changes.
  • Have your third-party accounts set up, API keys ready, and the required secrets added in Mistle for preview and production.
  • Go to cloudflare.com and sign up for the free plan.
  • Connect Mistle with your Cloudflare account:
    • Open the Main workstream
    • Go to Overview
    • Click Deploy
    • Mistle launches a Cloudflare login window so you can approve access to your account

​
Environment secrets in Mistle

  • Environment secrets are sensitive values (API keys, passwords, tokens) that should not live in your code.
  • Open the Variables and Secrets view in Mistle from the Deploy flow. Add values for preview and production as needed.
  • Once saved, Mistle sends the secrets to Cloudflare for that environment and hides the values—you won’t see them again.
  • Add any keys your app needs (auth providers, external APIs, email service) before deploying.

​
Deploy steps

  1. Run the deploy command provided for your project (or press the Deploy button if available).
  2. Wait for the success message; if you see errors, read the first line and retry after fixing.
  3. Open the live app link and click through the areas you changed.

​
What powers your deployed app

  • What it is: a serverless runtime that runs your bundled app close to users.
  • How it’s used: your code is packaged and deployed as a Worker; each request runs in this environment.
  • Why it matters: no servers to manage, fast cold starts, and global performance by default.
  • KV: a fast key-value store for config, flags, and cached data.
  • D1: a SQL database for relational data and queries.
  • R2: object storage for files, uploads, and media.
  • Why it matters: you get purpose-built storage options without standing up separate services.
  • What it is: Cloudflare maps your domain or a generated URL to the Worker.
  • How it’s used: routes send incoming requests to your app; custom domains can be attached.
  • Why it matters: makes the app reachable on the public web with proper URL handling.
  • What it is: Cloudflare’s command-line tool for Workers.
  • How it’s used: handles login, environment variables, and pushes preview/production builds.
  • Why it matters: provides the deployment, config, and environment plumbing behind the scenes.