Open
Conversation
…rate limiting with database-persisted throttling
…/RateGuard to Nginx and add health check endpoint
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #171
This pull request introduces a PostgreSQL-backed cache and rate-limiting system to enable shared throttling across multiple Uvicorn workers, and applies this rate limiting to critical API endpoints. It also includes environment and deployment improvements, such as default worker configuration and a new CLI installer for local development.
Core features and improvements:
1. Shared PostgreSQL-backed cache and rate limiting
lenny.core.cachemodule, providing aCacheclass for storing cache entries and aRateGuardFastAPI dependency for IP-based rate limiting using the database. This replaces in-memory rate limiting, ensuring consistent throttling across all workers.cachetable with relevant indexes for efficient lookups and expiry.2. Application of rate limiting to authentication and API endpoints
lenny.core.auth.OTPto use the new shared cache for rate limiting OTP send and verify attempts, replacing the previous in-memory logic. [1] [2] [3] [4]RateGuardas a dependency to the main API router (global limit), and to sensitive endpoints like/upload,/oauth/authorize, and/items/{book_id}/borrowwith route-specific limits. [1] [2] [3] [4] [5] [6]3. Deployment and configuration enhancements
0.1.4.4. Developer experience improvements
lennyCLI command, simplifying local development and common tasks.