tozo VS quart-rate-limiter

I've written an example with a Python backend here. The token itself is stored in a cookie, however there is an AuthContext used so the router etc knows whether to show a login page or not.

Thanks, there are more tutorials here and a full example React app if these are also useful.

I think I've gone down the same path you are on. I ended up with this pattern. I hope this is interesting.

I hope it is ok to recommend my own book. It describes the entire process to build a React+Quart web app running in AWS and served on a domain. The app built is viewable at tozo.dev and the code on github.

I don’t know the answer, but this might help you: https://github.com/pgjones/tozo

I've built tozo.dev to demonstrate how to build a (Progressive) web app with a Python-Quart backend, and a Typescript-React frontend running in AWS. I've included in the repository, github.com/pgjones/tozo everything needed to reproduce it i.e. all the code, the CI/CD actions, and the Terraform infrastructure definitions.

The app itself is running at tozo.dev with the full code on github.com/pgjones/tozo.

Thanks so much for buying my book, I hope it is good. Any questions about it are welcome here.

Quart-Rate-Limiter for rate limiting protection.