You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On https://release-monitoring.org/ when editing a project's details, it would be good to have a rate-limiting option for the custom backend. In particular, my project "trader" (https://release-monitoring.org/project/15397/) is currently scanned irregularly roughly every two to twenty minutes -- sometimes the gap is an hour or more, but sometimes it's just every few minutes. This seems rather excessive for a project that is released once a year or so! Providing an option like "scan once a day, once a week, once a month" (and shorter variants, too, for frequently updated projects) would be good.
For context, here is the Apache access log for 15th November:
This is strange, the project should be checked once per hour, and I already implemented #730, which should lower the amount of data to transfer. But it would be nice to have ability to choose how often the project is checked for new versions.
On https://release-monitoring.org/ when editing a project's details, it would be good to have a rate-limiting option for the custom backend. In particular, my project "trader" (https://release-monitoring.org/project/15397/) is currently scanned irregularly roughly every two to twenty minutes -- sometimes the gap is an hour or more, but sometimes it's just every few minutes. This seems rather excessive for a project that is released once a year or so! Providing an option like "scan once a day, once a week, once a month" (and shorter variants, too, for frequently updated projects) would be good.
For context, here is the Apache access log for 15th November:
The text was updated successfully, but these errors were encountered: