Skip to content

infra(docs): deploy wavehouse.dev via GitHub Actions (Cloudflare Workers) #148

Description

@EricAndrechek

Problem

The README and every doc page links to wavehouse.dev. The Astro/Starlight site lives in docs/, the Cloudflare Worker for .md content negotiation lives in docs/worker/, and docs/wrangler.jsonc declares the deploy target — but no GitHub Actions workflow publishes it.

Per CHANGELOG.md [Unreleased]:

Cloudflare Workers + Static Assets deployment via docs/wrangler.jsonc (no auto-deploy yet — wired up when the GH Actions workflow lands separately).

Until something publishes, wavehouse.dev either doesn't resolve or serves a stale version diverging from main. Every README link in the alpha announcement points at it.

Proposed Solution

Add .github/workflows/deploy-docs.yml:

  • Trigger on push to main (path-filtered to docs/**) and workflow_dispatch for manual reruns.
  • Run pnpm install --frozen-lockfile + pnpm build in docs/.
  • Deploy via cloudflare/wrangler-action@<full-sha-pin> using CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID repo secrets.
  • Concurrency group deploy-docs with cancel-in-progress: true so a rapid second push doesn't race.
  • Worker (docs/worker/index.ts) deploys alongside static assets so Accept: text/markdown content negotiation works in production.

Optional follow-up (not blocking): per-PR preview deploys via Cloudflare's preview URLs.

Acceptance criteria

  • A docs/-only push to main results in wavehouse.dev reflecting it within ~2 minutes.
  • Secrets documented in AGENTS.md § Repository Automation.
  • The .md twins / llms.txt / Accept: text/markdown content negotiation works against the deployed worker (not just wrangler dev).

Blocks

Alpha launch. Every doc URL we publish points at wavehouse.dev.

Activity

  1. coderabbitai commented on May 18, 2026

    @coderabbitai
    🔗 Related PRs

    #129 - ci: kill coverage Docker pull on PR runs + tighten claude-review group [merged]
    Wave-RF/WaveHouse-Demo#9 - ci(worker-deploy): bump Node to 22, drop fragile phase-run-bash-c wrapping [merged]
    Wave-RF/WaveHouse-Demo#10 - ci(worker-deploy): allow workflow_dispatch retrigger [merged]
    Wave-RF/WaveHouse-Demo#27 - worker: ship OTLP traces + loadtest reporting to Grafana Cloud [merged]
    Wave-RF/WaveHouse-Demo#30 - worker: POST stress-test region annotations to Grafana on loadtest stop [closed]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. moved this from Backlog to In progress in WaveHouse Task Boardon May 26, 2026
  3. moved this from In progress to In review in WaveHouse Task Boardon May 27, 2026
  4. added a commit that references this issue on May 27, 2026
    d50cd9a
  5. added a commit that references this issue on Jun 5, 2026
    280b2c9
  6. moved this from In progress to Done in WaveHouse Task Boardon Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/docsDocumentation, site/, READMEarea/infraCI, build, deploy, Docker, releaseenhancementNew feature or request

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions