neuroticnerd / dragoncon-bot Goto Github PK

Most of the exception handling should occur in the coroutines, especially since that is where any db interaction would occur to be able to store exception information in the db or send admin emails on errors.

Investigate whether it is feasible to just use the SQLAlchemy results model (potentially with some additional modifications) as the main results model that is passed between coroutines in the queue.

Improve the lifespan handling of the SQLAlchemy sessions to better conform to best practices for that library.

When availability is found, add parsing for the actual room data (price, type, etc.)

Add unit tests!

Implement a Django/Flask UI for the execution history stored in the db and possibly modifying settings or logrotate as well.

Investigate whether it would be better to store large exception traces or the raw HTML responses in a NoSQL db (mongodb, hbase, cassandra, etc.)

Provide easy ansible configuration for the bot (either in this repo or separately), including:

• db
• config file templates
• logrotate
• apt package setup
• python and pip installs

Make sure that the signed commits and committer email matches the GPG key (probably need to generate a new GPG key).