Originally created by @CoreBytee on GitHub (Nov 5, 2023).
Is there an option to configure rate limits on self-hosted instances?
If not, could it be added?
Thanks
Originally created by @CoreBytee on GitHub (Nov 5, 2023).
Is there an option to configure rate limits on self-hosted instances?
If not, could it be added?
Thanks
Necroposting a little, but this is definitely a must for low powered VPS's. I host my own instances and recently got one for my californian node, and downloading just one file that's audio only causes a CPU core to max out. (Out of the two that are there.) Implementing a queue or some kind of limit would definitely help mitigate this.
@ggtylerr commented on GitHub (Mar 17, 2024):
Necroposting a little, but this is definitely a must for low powered VPS's. I host my own instances and recently got one for my californian node, and downloading just one file that's audio only causes a CPU core to max out. (Out of the two that are there.) Implementing a queue or some kind of limit would definitely help mitigate this.
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.
Originally created by @CoreBytee on GitHub (Nov 5, 2023).
Is there an option to configure rate limits on self-hosted instances?
If not, could it be added?
Thanks
@2shiraz commented on GitHub (Nov 18, 2023):
It would be really cool if that could be set from docker-compose file
@ggtylerr commented on GitHub (Mar 17, 2024):
Necroposting a little, but this is definitely a must for low powered VPS's. I host my own instances and recently got one for my californian node, and downloading just one file that's audio only causes a CPU core to max out. (Out of the two that are there.) Implementing a queue or some kind of limit would definitely help mitigate this.
@KwiatekMiki commented on GitHub (Sep 1, 2024):
https://github.com/imputnet/cobalt/blob/current/docs/run-an-instance.md#variables-for-api
