asacristani / fastapi-rocket-boilerplate Goto Github PK

One suggestion would be to add elasticsearch support to the project so that if it is used, the structure already exists.

A suggested feature would be to add support for adapters that would allow integrating various forms of authentication, jwt, oauth, open id connect (oidc) and others

I recommend you add python 3.10 support if possible.
Most enterprises will be stuck to 3.10 due to their use of Ubuntu 22.04.

They don't upgrade things as often as they should. So its in the best interest of the maintainers to do so.

Include Pulumi config for deploying in AWS and test it.

Imitating Django, it could be amazing a CLI manager program for different things:

• Explore and manipulate the data though the ORM
• Handle migrations with Alembic
• Maybe remove the makefile and do everything in python?
• ...

Include integrity testing crossing though the api, celery and db.
Also with the admin dashboard.

https://pytest-mock-resources.readthedocs.io/en/latest/

In the Events section.

Add Sentry configuration and test it.

Now the message for delete and reverse_delete is the same (delete message).
It could be good to modify for reverse_delete being more accurate.

Hello, it would be great if the project supported Prometheus

Include logs using different levels for the following events:

• db interactions
• celery task interactions
• endpoint interactions

Create a relationship between models and their events for resolving events gathering faster.

When running through the installation guide, I needed to change pip to pip3 / python to python3 in order to get the setup running, as my local system is Mac Apple Silicon. Because Mac laptops have python 2.7 installed as base python version, I use shell aliases to map to the latest python/pip versions. Shell aliases don't appear to be expanded in Make, as /bin/sh is a non-interactive shell. How do you want your users to proceed here? Open to suggestions, thanks.

Issue Description: Currently, the FastAPI Rocket Boilerplate lacks rate limiting middleware, which is essential for controlling the number of requests a client can make to the API within a specific time frame. This issue aims to implement rate limiting middleware, allowing developers to configure and enforce rate limits on API endpoints.

Proposed Solution: Implement a rate limiting middleware that:

Supports rate limits based on IP address or user tokens.
Allows developers to configure rate limits for specific routes or groups of routes.
Provides clear documentation on how to configure and use rate limiting in the boilerplate.
Expected Impact: The addition of rate limiting middleware would enhance the security and reliability of the API by preventing abuse and ensuring fair usage of resources

Add Flower as a new service in Docker Compose and maybe in Pulumi configuration.

https://pytest-alembic.readthedocs.io/en/latest/index.html

A lot of lines to fix.

If you run trunk check -a, there are several issues to resolve.