Implemented cronjob for message deletion #207
Merged
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
AlexanderWangY
requested changes
Apr 1, 2024
* added pubsub for messages * test * finished pub sub * testing empty secret * Delete server/firebase-secrets.json * added pubsub for messages * test * rebased --------- Co-authored-by: AlexanderWangY <[email protected]>
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.
Cron-job for message deletion has now been implemented. The current deletion interval is set to 30s for development and testing purposes.
In addition, there is now a new
.envvariable that is required to be created:message_duration. Set it to 60000 for now.Also, added
firebase-secrets.jsonto the.gitignoreto avoid it getting tangled up in commits.Fixes #157.