Skip to content

DEPLOY.md

Latest commit

 

History

History
91 lines (75 loc) · 5.31 KB

DEPLOY.md

File metadata and controls

91 lines (75 loc) · 5.31 KB
Raw

Deploying Luna Web — Cloudflare Workers Builds (dashboard Git integration)

Two Workers, one repo, one host. Deploys run only through Cloudflare's dashboard Git integration (Workers Builds). Nothing in this repo — and no CI job — ever runs wrangler deploy; the configs under apps/*/wrangler.jsonc are the source of truth for names and asset behavior. Domains and routes are managed manually in the dashboard — the configs deliberately declare none, so a deploy can never re-assert or clobber manual domain settings.

Prerequisites

  • The ozer2.one zone lives in the connected Cloudflare account.
  • The GitHub repo shakedex/LunaApp is authorized for the Cloudflare GitHub App.

Worker settings (one Workers Builds connection per Worker)

In the dashboard: Workers & Pages → Create → Workers → Import a repository, pick shakedex/LunaApp, then configure each Worker:

Setting luna-web (app) luna-web-docs (docs)
Root directory apps/web apps/docs
Build command bun run build bun run build
Deploy command npx wrangler deploy (default) npx wrangler deploy (default)
Non-production branch deploy npx wrangler versions upload (default) npx wrangler versions upload (default)
Build watch paths apps/web/**, packages/core/**, bun.lock apps/docs/**, bun.lock
Production branch master master
API token auto-generated default auto-generated default

How it fits together

  • Bun is auto-detected from bun.lock; bun install run inside a workspace directory installs the whole workspace, so @luna-web/core resolves for the app build.
  • Vite+ needs no installer here: the vite-plus package ships the vp binary, so the build scripts' vp calls resolve from node_modules/.bin after install — Workers Builds settings stay exactly as the table above.
  • App Worker: the Cloudflare Vite plugin emits a flattened wrangler.json into the build output; the default npx wrangler deploy auto-locates it. SPA fallback (single-page-application) serves index.html for deep links; the router's not-found page handles the rest.
  • Docs Worker: plain static assets from apps/docs/dist, whose tree is nested as dist/docs/** (Astro outDir) to mirror the /docs URL path.
  • Routing (manual, one-time, dashboard-side): attach luna.ozer2.one to luna-web as a Custom Domain (Workers → luna-web → Settings → Domains & Routes). A Custom Domain creates the DNS record and certificate automatically — that is why a manually added subdomain works within seconds, while a bare route pattern does not: a route only binds an already-existing proxied DNS hostname to a Worker and never creates DNS. Then give luna-web-docs a route luna.ozer2.one/docs* (zone ozer2.one) — a route is required here because Custom Domains cannot carry path patterns; its DNS need is satisfied by the app's Custom Domain on the same hostname. Cloudflare matches the more specific /docs* route first, so the SPA never sees /docs requests.
  • Preview URLs: pushes to non-production branches upload a version and get a preview URL (preview_urls: true); the production site stays off workers.dev (workers_dev: false).
  • The ~31 MB ffmpeg core is not deployed — it rides jsDelivr + the Cache API at runtime (see spec §12). The largest deployed asset (~2.5 MB mediainfo wasm) is far under the 25 MiB/file Workers limit.

Local verification (no deploy)

# App: build + preview the built Worker (SPA fallback live)
cd apps/web && bun run build && bun run preview

# Docs: build + serve the static Worker locally
cd apps/docs && bun run build && bunx wrangler dev
# then check /docs/ and /docs/<missing> (styled 404)

Versioning (ZeroVer)

Luna Web follows ZeroVer (0ver): the major version stays 0 permanently; releases are 0.MINOR.PATCH (MINOR for features, PATCH for fixes). A release is a bump of apps/web/package.json version — it surfaces in the app header (__APP_VERSION__), the Credits page, and the PDF footer stamp. There will never be a 1.0.

See RELEASING.md for the release workflow (bun run release <minor|patch>) and the curated changelog that publishes to /docs/changelog/.

First-deploy checklist

  1. Connect both Workers per the table above; push (or "Retry build") on master.
  2. Both builds green in Workers Builds.
  3. Attach the domain/route manually per the Routing bullet above: Custom Domain luna.ozer2.one on luna-web; route luna.ozer2.one/docs* on luna-web-docs.
  4. https://luna.ozer2.one serves the app; a deep link (e.g. /settings) loads.
  5. https://luna.ozer2.one/docs/ serves the docs; /docs/<garbage> shows the styled 404.
  6. Push a throwaway branch → preview URL appears on the build.