Possibility of exposing the db you're using for emails as an API?

Wanted to try and knock up a slightly more user friendly site for the data and an API would be a great way to just stand up a netlify/github pages/serverless frontend.

Obviously understand if you're looking to keep it lean and low cost, in which case i'll just stand up a server 😁

Fully Parsing Exposure Sites

Purpose

This fork was made to properly parse the start times, end times, and locations of COVID-19 exposures in WA. The idea is people could also use it as a Python module to process exposures themselves for any purpose (for example mapping) as opposed to just notifications, and notifications would be able to be formatted more consistently.

Changes

Basically what has changed is

• The project has been split into three separate files and mostly rewritten
  • One contains classes and tools for exposure sites (exposure_tools.py)
  • Another parses exposure sites using these tools (exposure_parser.py)
  • And the third stores these sites in a database and sends new exposures to Discord (discord_notify.py)
• Exposure notifications should now use the Exposure class of exposure_tools.py to have a standardised format
• All notification outputs other than Discord webhooks have been removed (that was all I needed, but the others can be re-implemented fairly easily)
• The Curtin University exposure function isn't called anymore because the table has been removed from the website

Other

This isn't so much related to the pull request but something I would have tried to do later: I'm not sure what the process is, but it could be an idea to try add the module to PyPI so that it could be used more effectively as a module. The notification script could be used as a script within the package and exposure_parser.py could be used to get exposure sites and process them in Python

Add support via Discord's webhook API Note that Discord only allows messages up to 2000 characters, so I've configured it to split by each exposure notification and post individually with a 2 second delay to hopefully avoid rate limits. In my testing, a first time run will attempt to post ~200 messages and get rate limited by Discord's API, but additions to the exposure list seem fine. I'd recommend not enabling Discord until you've run at least once and created the database.

New columns: first_seen and last_seen for entries that disappear or to show when they were last seen.

Also updated formatting for multiple line breaks, line breaks at the start of entries, and tidied up flow so fields only need to get cleaned once.

Added a method to chunk to the nearest alert ending; can be modified to change delimeter or max length as needed but defaults work with discord's 2k limit.