chore(website): Increase daily rate limit from 10 to 30

[yamadashy]

Increase the website's daily rate limit from 10 to 30 requests per user to accommodate growing usage.

Checklist

• Run npm run test
• Run npm run lint

---

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3c0681d0-1a04-4270-81c9-20a32b9a9a43

📥 Commits

Reviewing files that changed from the base of the PR and between fb24e64 and 82c465b.

📒 Files selected for processing (1)

• website/server/src/utils/dailyRateLimit.ts

---

📝 Walkthrough

Walkthrough

The daily rate limit configuration is updated by increasing the fixed-window rate limit threshold from 10 to 30 requests per day in the rate limiting utility.

Changes

Cohort / File(s)	Summary
Rate Limit Configuration website/server/src/utils/dailyRateLimit.ts	Increased the DAILY_LIMIT fixed-window rate limit value from 10 to 30 per day.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/website-increase-daily-limit

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

Review Summary

PR: chore(website): Increase daily rate limit from 10 to 30
Status: ✅ Approved — No issues found

This is a clean, minimal configuration change — a single constant updated from 10 to 30 in website/server/src/utils/dailyRateLimit.ts.

Detailed Analysis

Code Quality

Clean and minimal. The change is scoped to exactly one constant, which is the right approach since DAILY_LIMIT is already well-named and centralized.

Security

No security concerns. The rate limit is being relaxed (10 → 30), not removed. The Upstash-backed rate limiter, Redis credentials check, and per-user fixed window logic all remain intact. A 3x increase is reasonable and still provides abuse protection.

Performance

No performance impact. The rate limit logic and Redis interaction are unchanged.

Testing

For a configuration constant change like this, the existing test coverage is sufficient. No new tests needed.

Conventions

• Commit message follows Conventional Commits ✅
• PR checklist completed ✅
• Scope is minimal and focused ✅

LGTM — straightforward config bump to accommodate growing usage. 👍

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request increases the daily rate limit from 10 to 30. Feedback suggests making this value configurable via an environment variable to allow for operational adjustments without requiring a new deployment.

[gemini-code-assist]

For better flexibility and to avoid future code changes for adjustments, consider making the daily rate limit configurable via an environment variable. This would allow changing the limit without a new deployment, which is a common practice for values that might change based on operational needs.

Suggested change

	const DAILY_LIMIT = 30;
	const DAILY_LIMIT = Number.parseInt(process.env.DAILY_RATE_LIMIT ?? '30', 10);

[github-actions]

⚡ Performance Benchmark

Latest commit:	82c465b chore(website): Increase daily rate limit from 10 to 30
Status:	✅ Benchmark complete!
Ubuntu:	1.44s (±0.02s) → 1.44s (±0.03s) · -0.01s (-0.3%)
macOS:	0.87s (±0.09s) → 0.87s (±0.04s) · +0.00s (+0.3%)
Windows:	1.81s (±0.07s) → 1.81s (±0.06s) · +0.01s (+0.3%)

Details

• Packing the repomix repository with node bin/repomix.cjs
• Warmup: 2 runs (discarded), interleaved execution
• Measurement: 20 runs / 30 on macOS (median ± IQR)
• Workflow run

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.