<!--
Thank you for doing recipe maintenance work!
Please mark all checklist items which are relevant for your changes.
Please remove the checklist items which are not relevant for your changes.
Feel free to remove this comment.
-->
* [x] I have deployed and tested my changes
* [x] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
* [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
the middleware is enabled by default but only applies when applied to every service or individual services export it as a label.
there's another rate limit option to limit by host, which i've seen recommendations for nginx to enable in parallel to rate limits by ip with a higher limit. should i add that too?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
the middleware is enabled by default but only applies when applied to every service or individual services export it as a label.
there's another rate limit option to limit by host, which i've seen recommendations for nginx to enable in parallel to rate limits by ip with a higher limit. should i add that too?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
there's another rate limit option to limit by host, which i've seen recommendations for nginx to enable in parallel to rate limits by ip with a higher limit. should i add that too?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
Let's add those in another pr
Could you add a release note? Would be nice to tell people about this :)
Also could you add a note on how to debug this setting? E.g. if there is a relevant metric about rate limiting
> there's another rate limit option to limit by host, which i've seen recommendations for nginx to enable in parallel to rate limits by ip with a higher limit. should i add that too?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
Let's add those in another pr
Could you add a release note? Would be nice to tell people about this :)
Also could you add a note on how to debug this setting? E.g. if there is a relevant metric about rate limiting
just discovered there's another strategy to group by request header which isn't documented further, but it looks like it could apply rate limits by specific headers, like user agents.
just discovered there's another strategy to [group by request header](https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/ratelimit/#opt-sourceCriterion-requestHeaderName) which isn't documented further, but it looks like it could apply rate limits by specific headers, like user agents.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
abra.shthe middleware is enabled by default but only applies when applied to every service or individual services export it as a label.
there's another rate limit option to limit by host, which i've seen recommendations for nginx to enable in parallel to rate limits by ip with a higher limit. should i add that too?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
2b40910287to28778ca411@@ -25,0 +26,4 @@rateLimit:average: {{ or (env "RATE_LIMIT_AVERAGE") "100" }}burst: {{ or (env "RATE_LIMIT_BURST") "200" }}period: "1s"Can you make this configurable too
@@ -252,0 +254,4 @@# You can enable universal rate limits by setting RATE_LIMIT_EVERYTHING# to true, otherwise each app needs to export their own middleware labels.## https://doc.traefik.io/traefik/reference/routing-configuration/http/middlewares/ratelimit/Can you add an example on how to enable a single service via the label?
it's included on the docs and the recipe has to support it, do you think it's not enough pointer?
also it supports redis for shared rate limits, so we could collaboratively rate limit between servers.
Let's add those in another pr
Could you add a release note? Would be nice to tell people about this :)
Also could you add a note on how to debug this setting? E.g. if there is a relevant metric about rate limiting
28778ca411to21ea1dd698@fauno ping :)
pong! i'll be back in a couple hours :)
added release notes!
just discovered there's another strategy to group by request header which isn't documented further, but it looks like it could apply rate limits by specific headers, like user agents.