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
- TablesDB `updateRows` returns `database_...
Hi Appwrite team! I’m seeing a strange issue with TablesDB bulk row updates on a self-hosted Appwrite instance. **Environment** - Appwrite self-hosted `1.9.0` ...
- [SOLVED] Realtime Missing Channels
```js useEffect(() => { let subscription: RealtimeSubscription; async function loadChips() { try { const {rows: chi...
- Update row sheet not loading
After right clicking a row header and click update, the sidebar fails to load (never-ending skeleton)