IATI Canary leans heavily on some of the somewhat hidden outputs of IATI Data Dump – specifically, the various error logs that are stored as GitHub gists here.
It might be nicer to store an error history for each dataset. But it’s not feasible to do that whilst staying within the 10,000 database row limit that’s imposed on the free tier of postgres on Heroku.
cp .env.example .env…and modify as appropriate.
Install dependencies using pipenv:
pipenv installAnd set up database:
pipenv run flask db upgradeRun a local development server:
pipenv run flask runVarious commands need to be run as cron tasks. Specifically:
pipenv run flask cleanup
pipenv run flask fetch-errors
pipenv run flask send-emails