Host on Cloudflare

Deploy static sites globally with Workers, Pages, or both. heavens.tools runs on Cloudflare Workers with static assets — this is the same stack you can use for your builder exports.

When to use Cloudflare

• You own a DNS domain (yoursite.com) on Cloudflare
• You want fast CDN, free SSL, and simple deploys
• You're okay with centralized hosting (vs pure IPFS)

Option A — Cloudflare Pages (simplest)

1. Export HTML from the site builder (Download button) or push a folder to GitHub.
2. In Cloudflare Dashboard → Workers & Pages → Create → Pages → Connect Git or direct upload.
3. Set build output to your static folder (or leave empty for pure HTML upload).
4. Add a custom domain under Pages → your project → Custom domains.
5. Cloudflare creates DNS records automatically when the zone is on your account.

Option B — Cloudflare Workers + Assets (what Heavens Tools uses)

1. Install Wrangler: npm install -g wrangler
2. Login: wrangler login
3. Project structure:

   my-site/
     wrangler.toml
     src/index.js      # optional routing
     public/           # your HTML, css, js
       index.html

4. Minimal wrangler.toml:

   name = "my-site"
   main = "src/index.js"
   compatibility_date = "2024-08-01"
   
   [assets]
   directory = "./public"
   binding = "ASSETS"
   
   [[routes]]
   pattern = "www.yoursite.com/*"
   zone_name = "yoursite.com"

5. Deploy: wrangler deploy

DNS tips

• Remove old CNAMEs to dead hosts (e.g. expired CDN) before attaching Worker custom domains.
• Proxied records (orange cloud) route through Cloudflare — required for Workers zone routes.
• API token needs Zone DNS Edit + Workers Scripts Edit for automated fixes.

Combine with ENS

Pin the same static export to IPFS, set your ENS content hash, and use name.eth.limo as a decentralized mirror while DNS serves yoursite.com on Cloudflare. See DNS × IPFS × ENS.