Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/fcm lifecycle #213

Merged
merged 6 commits into from
Feb 9, 2025
Merged

Feat/fcm lifecycle #213

merged 6 commits into from
Feb 9, 2025

Conversation

kiritowu
Copy link
Collaborator

@kiritowu kiritowu commented Feb 6, 2025

Close #211

Changes:

  • Add new table notification_tokens to store unique token for each user.
  • Create backend endpoints to register, deregister and cleanup old tokens after 30 days.
  • Update frontend components to register token on request, and deregister token on signout.

@kiritowu kiritowu self-assigned this Feb 6, 2025
@kiritowu
Copy link
Collaborator Author

kiritowu commented Feb 6, 2025

After feat/notification is deployed, a cloud scheduler cron job will be deployed to check for outdated tokens every day.

@kiritowu kiritowu merged commit f8aa99d into feat/notification Feb 9, 2025
1 check passed
@kiritowu kiritowu deleted the feat/fcm-lifecycle branch February 9, 2025 12:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant