vjrj
d20e168c90
Sustituye el envío de push por la API legacy de GCM (muerta desde jun-2024) y saca el envío del observer de Meteor a una cola BullMQ controlada. - poller: consume 'notifications' pendientes (campos correctos; el cron viejo tenía un typo nofitied/emailNofitied que nunca casaba) - fcm-worker: firebase-admin (FCM HTTP v1), payload compatible con la app Flutter (FLUTTER_NOTIFICATION_CLICK, collapseKey=_id, data); purga tokens muertos sin reintentar - email-worker: nodemailer + plantillas new-fire portadas verbatim - idempotencia persistente: notification_sends, indice unico (notificationId, channel) -> sobrevive reinicios y replays - salvaguardas anti-spam: modos dry-run/shadow/canary/full, exclusion mutua por canal (OWNED_CHANNELS + notifDisabledChannels en Meteor), kill switch, limites por usuario/dia y circuit breaker por batch - docs/legacy-behavior.md (caracterizacion) + docs/rollout.md - 47 tests (vitest + mongodb-memory-server), typecheck y build OK - deploy: systemd + pm2 (Node 22 standalone) Falta el service account de Firebase para envio real de push (pedir al usuario).
14 lines
460 B
Text
14 lines
460 B
Text
Hey, {{firstName}}!
|
|
|
|
{{message}}
|
|
|
|
More information about this fire: {{fireUrl}}
|
|
|
|
Isn't it a forest fire? In the previous link you can tell us what kind of fire it is and help us improve our notifications.
|
|
|
|
You can also add comments on that link if you have additional information about this fire (how to access that area, if you know how the fire originated, etc).
|
|
|
|
Thanks!
|
|
{{applicationName}} Team
|
|
|
|
Manage your subscriptions to these fire alerts: {{subsUrl}}
|