Now the Heroku-hosted LibraryHippo can perform periodic tasks, send e-mails, and
scrape the Waterloo Public Library's website. All it needs is a datastore to tie
these concepts together into a decoupled "push card status to patrons" pipeline.
Now that the toy LibraryHippo on Heroku is sending periodic e-mails, it's time
to provide it with meaningful content to send, by having it scrape a library's
website. This should be relatively straightforward, but there's some risk as
it's not an operation covered in
The Flask Mega-Tutorial.
Having established that a Flask app running on Heroku can send e-mail, I turn my
attention to having LibraryHippo do so periodically. The approach will be to
change the e-mail-sending to be something that can more easily be triggered from
the outside, and then triggering it from from time to …
After getting a do-nothing web app running on Heroku, I think the riskiest
requirement is having a scheduled job for LibraryHippo to check families' status
and notify them. However rather than trying to satisfy that requirement, this
time I'm going to try to set up email sending, mostly because it …