#how to fix appwrite rate limit exceeded

43 messages · Page 1 of 1 (latest)

elder elk
ivory pawn
#

Two options:

  1. Not sending a huge amount of requests (if needed to make bulk edit, make it through a function)

  2. Disabling your appwrite instance rate limiting
    https://appwrite.io/docs/environment-variables#general

Go to your .env file and change the variable called _APP_OPTIONS_ABUSE to disabled

Formatted like that: _APP_OPTIONS_ABUSE=disabled

elder elk
#

where do i write this _APP_OPTIONS_ABUSE=disabled

#

which env file?

ivory pawn
#

You can edit it in the file called docker-compose.yml

elder elk
#

ohh

ivory pawn
#

Does that solve your problem? 😃

#

@elder elk

elder elk
#

nope i dont know how to use docker

#

i dont have clear idea what to do with this _APP_OPTIONS_ABUSE=disabled

ivory pawn
#

Yust search for a file called docker -compose.yml in your appwrite installation folder

elder elk
#

i didnt installed docker

ivory pawn
#

Then you're using appwrite cloud, or installed through the appwrite one-click digitalocean installer?

elder elk
#

i am using appwrite cloud

ivory pawn
#

Then you can't disable rate limiting

elder elk
#

ohh

#

after hosting my app my users may request more than 10 requests

ivory pawn
#

It's only available in appwrite self-hosted. If you need to make bulk for example of documents, then make it through a functions, so users trigger the function and then such function generated the documents, etc

elder elk
#

ohh i got it

#

my app is related to book pdf notes

#

making an app for campus Notes

ivory pawn
#

You mean uploading multiple documents then?

elder elk
#

so users request api calls everytime to get access of notes

elder elk
#

help me out please

ivory pawn
#

You don't make a request for every note, you make a request to get access to a bunch of documents

#

So that way you'll not be rate-limited

elder elk
#

yes

ivory pawn
#

Also never download if there are 10000 documents, all of them at once

elder elk
#

my app has 5 level of hirerchy to access pdf file like
user>Branch>Year>Semester>Subjects>(pdf of particular subject)
branch can be CSE,IT,ECE,EEE,CIVIL,MECH
Year can be 1,2,3,4
Semester can be 1,2,3,4,5,6,7,8
subjects can be multiple max 10 for each semester

and at the end the pdf will be available for particular subject

ivory pawn
#

Each of them is a collection

#

And each input is a document

#

Just imagine like if it was a SQL database (appwrite database is SQL, except API) so every table is a collection and each row is a document

elder elk
#
  • users (collection)
    • {userID} (document)
      • branches (subcollection)
        • {branchName} (document)
          • years (subcollection)
ivory pawn
#

You can't make subcollections

elder elk
#

okay

#

how do you got this much knowledge about appwrite?

ivory pawn
#

Reading docs and making an app with it

#

Also seeing appwrite blog

#

But I have too doubts while structuring data 😅
Not about how to structure it, but more about how to make it be efficient

elder elk
#

ohh