You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: document Hosted rate-limit env vars and Retry-After behavior #37
P1-2 shipped in-process rate limits (apps/api/src/mutiny_api/rate_limit.py) with env knobs (MUTINY_RATE_LIMIT_*, Retry-After, 429 rate_limit_exceeded). Operator-facing docs are thin relative to code — SECURITY.md mentions order of middleware, but contributors lack a single field guide like the health-doc issue (#8).
Operators tuning single-tenant Hosted need to know defaults and that limits are not distributed.
Proposed direction
Add docs/RATE_LIMITS.md (or SECURITY subsection) listing env vars, defaults, identity keying (Bearer vs anonymous), and client expectations for Retry-After. Link from docs/README.md.
Acceptance criteria
Env vars + defaults documented from code (not invented)
Explicit “in-process / per-process only” warning
Linked from docs hub and/or SECURITY.md
No behavior change required
Testing expectations
Docs-only; optional assert that documented env names exist as constants in rate_limit.py.
Opened PR #152 documenting Hosted rate-limit settings, defaults, identity keying, per-process limits, and Retry-After behavior. Values verified against code; all CI checks passed. No runtime behavior changes.
Activity
BasilZafar11 commentedon Nov 15, 2026
Opened PR #152 documenting Hosted rate-limit settings, defaults, identity keying, per-process limits, and Retry-After behavior. Values verified against code; all CI checks passed. No runtime behavior changes.