feat:alarm cronjob #220
Draft
feat:alarm cronjob #220
+64
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Antonwy What do you think would be a sane architecture to deliver alerts to both ios and android users (especially given the upcoming flutter-schenanigans)? |
|
@Antonwy small ping |
CommanderStorm
force-pushed
the
feature/alarm-cronjob
branch
from
99d519a
to
f50ed82
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR migrates the alarm cronjob.
To prevent duplicate alerts, this can only be merged if the cronjob is removed in the v1 backend