This post and this comment inspired me to add an option to reject requests for those expensive operations (blame, arbitrary diffs/rev trees, grep etc) in my personal cgit fork. I haven’t been hit by nasty crawlers particularly hard, but checking my nginx access log consistently shows several requests per second and most of them are to such URLs, so this should help reduce load on my cheap VPS. (disclaimer: i mostly vibecoded it)
I assume this the next escalation level to defend against bots. To be used when I want to publish a repo but not DDOSed?
Doesn’t Forgejo provide an options to restrict the public web interface to not show individual commits and stuff just like reporat, grubby, etc?
score 1 · canonical
That’s certainly part of it. Reducing resource usage, especially on low end servers is another plus!
score 1 · canonical
This post and this comment inspired me to add an option to reject requests for those expensive operations (blame, arbitrary diffs/rev trees, grep etc) in my personal cgit fork. I haven’t been hit by nasty crawlers particularly hard, but checking my nginx access log consistently shows several requests per second and most of them are to such URLs, so this should help reduce load on my cheap VPS. (disclaimer: i mostly vibecoded it)
score 1 · canonical