Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Post Updated 9/24/2022
a Rework of #728 to use Redis TTL
Function
when bot is started, the reminders Table from Postgres is cached to redis and refreshed once a day (also checks for stale reminders that may still be in the Postgres DB due to a possible missed trigger event and either remove them or set up for the next alarm)
uses Redis TTL and a keyspace event listener to trigger the notifications.
uses Direct Messages to function, and was designed to be personal reminders, so most of the responses are ephemeral.
You can set reminders by Text Channel or Direct Message.
All reminders are Direct Messages (can't annoy other people)
if it had a repeat options, then create a new db entry when message is sent (or during clean up check at start up or daily check)
Caveats
Reminders being deleted when the Redis Server is Hosted on an Ephemeral Web Services like Heroku( resolved in 9833b67 )/reminder save-timezone
)Objectives
event
andtime
.env
variableTZ=<tz-database-name>
when using Docker Only)*Monthly option can only be used if the desired Day is less than the 28th
Much Love
-Bacon