[meta] active scraper that doesn't run by default
patcon opened this issue · comments
I was hoping to move toward having long-running historical scrapers (like disabled/ca_on_toronto/events.py) that aren't run on pupa update ca_on_toronto but which can be run manually with pupa update ca_on_toronto events.
Thoughts? And if you think it makes sense, would this be something sensible to add here, or in pupa?
Add it here. Only the "people" scrapers run on a cron schedule on Heroku currently. I can configure additional scrapers, and those scrapers can accept command-line options to not do historical scrapes.
👍 Thanks!
I think this is resolved.