feat(server): allow ratelimiting to be explicitly disabled #3757
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
We may wish to enable the rate limiter in some testing environments, and we may wish to disable the rate limiter in some non-testing environments (e.g. development).
The rate limiter was previously implied based on whether NODE_ENV is 'test', which may not be desired behaviour.
Changes:
RATELIMITER_ENABLED
boolean environment variable, default istrue
.server.ratelimiting.enabled
to configure the same, default istrue
.To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References