
I am developing a fun little side-project using this great Baas. I am using react and wrote a hook to get a session (currently with a fake user/password hard coded for development, will incorporate correct login later on). However, during development I am refreshing the app pretty often and I always get a new session. After a few times, the rate limit kicks in. Am I doing something wrong. Can I somehow disable the rate limit - btw. I am hosting appwrite in my homelab and I see no problem currently with unlimited requests, because this application is not open to public.

Why not saving the session?

If self-hosted, yes, you can disable rate limit. If you're in cloud, not possible (note that for the Hackathon you need to use appwrite cloud and not self-hosted)

You mean saving the session in local storage somehow?
Can you give me a hint, how to disable the rate limit?

Use account.get() to see if user has logged in previously and a session already exists

Instead of always creating a new sesion

@DS I figured this one out of you still need help
Recommended threads
- login backend and frontend
I'm using Remix, as my Backend (node). and react on my frontend. Until now, i did SSR login. saved the secret.. and it's fine. For many simpler requests i wish...
- Stuck in Readonly Mode After Pro Subscri...
Hello team, I really need some urgent help. I recently resubscribed to the Pro plan hoping to get back into a project I created a while ago, but I'm still unab...
- Missing C++ libstdc library in Python fu...
I have a function running Python 3.12 which suddenly started dumping errors (as of today; it worked yesterday). I hadn't changed any code so I found this odd, b...
