On Wed, Dec 04, 2019 at 04:58:20PM -0500, Andrew Engelbrecht wrote:
Hello Pagure devel list,
Sorry if this isn't quite the right place for this question.
The FSF is looking into hosting our own Web based SCM service, possibly
using Pagure. We would like to how the pagure.io team handles spam,
abuse, and overly large repos on your site. We expect that this could be
an issue, and that it would be critical for keeping our new site alive
and well. Any input on this topic would be very helpful.
Hi Andrew,
Thank you for your interest in pagure.
We have not had to much spam on pagure.io yet (or it hasn't been reported), but
pagure has a mechanism for admin to block an user for a definite amount of time
(from a day to a century or more) so we've used that mechanism in the few cases
of spam we dealt with.
For overly large repo, we've mostly tested with the kernel. Pagure is kinda slow
then but it works. Issue tracking should not be an issue, PRs may be fairly
slow.
There is a staging instance at
https://stg.pagure.io if you want to play with
pagure without breaking pagure.io (but please let us know if you break that
instance :)).
Hoping this helps,
Pierre