docs+script: harden deploy-new-server.sh and document it - #3
Conversation
- Tighten Caddyfile sed substitution: use literal `{$CKP_DOMAIN:example.com}`
match instead of a fragile regex chain. Quiets shellcheck SC2015.
- README: link the wrapper from the production-deploy section.
- docs/setup-server.md: add Step 0 fast-path with curl-pipe usage.
- docs/knowledge.md: surface the wrapper in the lifecycle table.
- docs/known-issues.md: mark the previous multi-step bootstrap as resolved.
- docs/guidelines.md + docs/approach.md: explain why this script lives
outside the one-script lifecycle rule (install-only glue, runs above
the target).
- CLAUDE.md: add a "deploy to a new server" section.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ 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 |
2 participants
Summary
scripts/deploy-new-server.sh(literal placeholder match, no SC2015 warning)Test plan
🤖 Generated with Claude Code