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
- Anyone manage to get a slack-bot working...
I'm trying to setup a bot the send and retrieve slack messages to a chat in my site. I've failed with SSE and appwrite functions soo far... i'll trying polling ...
- [Sites] Deployment finished but site is ...
The deployment finished and is active but the site shows timeout error.
- Does Appwrite allow SSE ?
i'm trying to setup a slack bot on my site. Your deployed SSE endpoint is returning a non‑SSE response …and the browser immediately closes the connection. read...