Conversation
- ci.yml: build + test on node 20.x/22.x for pushes and PRs - release.yml: npm publish with provenance on GitHub release/tag - test/e2e.test.ts: spawns the real built daemon as a child process and exercises deploy, public fetch, auth, touch, protected deploys, and removal end-to-end Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds a 100% local, token-authenticated admin page served by the internal API at GET /admin?token=<token>. Lists deployments with slug/name/file, relative created/expiry times, a lock indicator for protected deploys, per-row Delete, and a preview link — auto-refreshing every 10s, inline CSS/JS only (no CDN). Factors safeEqual() out of isAuthorized() and reuses it for the query-param token check without bypassing the Host loopback guard. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
--qr renders a terminal QR code for the deployed URL (per file, on multi-deploy). --watch keeps the process alive and redeploys in place (same slug) on source change, debounced 300ms, for a single file or directory bundle; restricted to exactly one target and incompatible with stdin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Reclaim freed bytes when replacing content without versioning - Hide access key from list() output; expose only protected flag - Serve protected content with private, no-store Cache-Control - Validate key type on API update (must be string) - URL-encode slug in touch endpoint - Escape paths in systemd unit file generation - Clean up stale PID file on status - Re-enforce 0600 permissions on existing token - Better error for empty token file
|
Warning Review limit reached
Next review available in: 28 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (26)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
Summary
deploy --qr— prints a scannable QR code for the deployment URL (requiresqrcode-terminal)deploy --watch— watches a file/directory and redeploys on change with 300ms debounce; combine with--qruptool admin— opens a 100% local, token-authenticated admin web UI listing all deployments with delete and previewci.yml) runs on push/PR for Node 20.x/22.x; Release (release.yml) publishes to npm on tag pushtest/e2e.test.ts) drives the real daemon as a child process through deploy/fetch/auth/touch/protect/removelist()responses (exposed asprotected: boolean)private, no-storecache-control; token file re-chmodded 0600 on read; empty token file treated as unauthenticated; timing-safe token comparison refactoredencodeURIComponent(slug)in touch route; proper 413 status for oversized bodies; base64 size calculation accounts for padding; stale PID file cleanup on stop; systemd unit escaping for paths with special chars;readLogTailreads bounded chunk instead of whole fileTesting
npm test)/admin— rejects missing/bad token, serves HTML with correct token--qrand--watchflags exercised manually; watch redeploy tested via file modificationprivate, no-storeheader confirmed on protected deployments via curl