[kevinelliott]

Requested by Kevin · project thread

Summary

Follow-up to #25. The map now deploys the same way the globe does: the Cloudflare Pages project airframes-coverage in the Airframes account is connected to this repository and builds on every push and pull request. It is live at https://airframes-coverage.pages.dev/. That makes the wrangler-based workflow from #25 redundant, and it could never upload anyway because the repository has no Cloudflare secrets.

• Removes .github/workflows/deploy-map.yml.
• Replaces the deployment section of the README with the Pages project build settings.
• Replaces coverage-api.airframes.io with staging-coverage.airframes.io in the README and in the Map CI build args. coverage-api.airframes.io has no DNS record, so every build that used it showed an empty map. The coverage service currently runs only on the staging cluster, where staging-coverage.airframes.io serves the API under /api/ and the WebSocket at /ws.

Pages project settings (as configured)

Setting	Value
Root directory	map
Build command	npm run build:static
Build output directory	out
NODE_VERSION	24
NEXT_PUBLIC_COVERAGE_API_URL	https://staging-coverage.airframes.io
NEXT_PUBLIC_WS_URL	wss://staging-coverage.airframes.io/ws

Without the API variable the build points at http://localhost:3002. Both are set for Production and Preview.

Verification

• Production deployment of main succeeded, and the page returns 200.
• The deployed bundle contains staging-coverage.airframes.io and no coverage-api.airframes.io or localhost:3002.
• https://staging-coverage.airframes.io/api/v1/stats and /api/v1/stations return 200 JSON with access-control-allow-origin: *.
• Not verified: the page has not been opened in a browser against live data, and the WebSocket was not exercised (the map polls /api/v1/activity; NEXT_PUBLIC_WS_URL is not referenced by the current client code).

Screenshots

None: this changes a workflow file, CI build args and the README only, with no UI change. The map's screenshots are in #25.

🤖 Generated with Claude Code

https://claude.ai/code/session_01PS44Q7WRmAzMJLhi44dzdo

Summary by CodeRabbit

• Deployment
  • Removed the automated map deployment workflow.
  • Updated map build and Docker deployment settings to use the staging coverage API and WebSocket service.
• Documentation
  • Updated Cloudflare Pages setup guidance, including build settings and staging service URLs.
  • Clarified that Pages can publish production builds from main and previews for pull requests, and documented the localhost fallback when API variables are unset.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The map workflow now uses staging coverage API and WebSocket URLs. The README describes Cloudflare Git integration for Pages deployment, and the GitHub Actions deployment workflow was removed.

Changes: Map deployment

Layer / File(s)	Summary
Set staging service URLs .github/workflows/map.yml	The workflow-level environment and Docker build arguments now use the staging coverage API and WebSocket URLs.
Update Cloudflare Pages deployment path README.md, .github/workflows/deploy-map.yml	The README documents Cloudflare Git integration and its Pages settings. The GitHub Actions map deployment workflow was removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: Minimal · up to 20749

This change moves map deployment to Cloudflare Pages Git integration and points builds at the staging coverage service. The repository changes are low risk. The Pages project must be created and configured separately before deployments occur.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title states the main change: the map deployment moves from a wrangler-based GitHub Actions workflow to the Cloudflare Pages Git integration. The raw summary confirms the deploy workflow was delet…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.

Full details: Title check

Explanation

The title states the main change: the map deployment moves from a wrangler-based GitHub Actions workflow to the Cloudflare Pages Git integration. The raw summary confirms the deploy workflow was deleted and the README now describes Git integration, so the title matches the changeset.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 29a64dcc-bc15-48e9-85ae-10051e5dd76e

Commits

Reviewing files that changed from the base of the PR and between 8317248 and 20749b5.

Files selected for processing: 3

• .github/workflows/deploy-map.yml
• .github/workflows/map.yml
• README.md

Files with no reviewable changes: 1

• .github/workflows/deploy-map.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

[cursor]

Approved. Cursor Bugbot completed successfully with no findings that need human review, and no approval policy requires extra review. This automation is approving based on that signal.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[cloudflare-workers-and-pages]

Deploying airframes-coverage with    Cloudflare Pages

Latest commit:	20749b5
Status:	✅  Deploy successful!
Preview URL:	https://f5061d6f.airframes-coverage.pages.dev
Branch Preview URL:	https://claude-project-thread-xlxhmp.airframes-coverage.pages.dev

View logs