feat: Push-Notifications scharfschalten (echtes Web Push mit VAPID) - #11
Merged
Conversation
Die bisherige send-push-Version schickte nur rohes fetch an den Endpoint — ohne VAPID-Signierung und Payload-Verschluesselung, was Push-Dienste (FCM, Mozilla, Apple) ablehnen. Jetzt via npm:web-push@3.6.7: - webpush.setVapidDetails() aus VAPID_PUBLIC_KEY/PRIVATE_KEY/SUBJECT - webpush.sendNotification() pro Subscription (VAPID + aes128gcm) - 404/410 -> abgelaufene Subscription loeschen Voraussetzung: VAPID-Secrets in Supabase + VITE_VAPID_PUBLIC_KEY in Vercel. https://claude.ai/code/session_01G1v5ZGvnrS5hb6eX2hfxKb
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Was
Die
send-push-Edge-Function macht jetzt echtes Web Push. Die bisherige Version schickte nur ein rohesfetchan den Push-Endpoint — ohne VAPID-Signierung und ohne Payload-Verschlüsselung. Das lehnen alle Push-Dienste (FCM/Chrome, Mozilla, Apple) ab, es kam also nie eine Notification an.Neu via
npm:web-push@3.6.7:webpush.setVapidDetails()aus den Env-Secretswebpush.sendNotification()pro Subscription (VAPID-JWT +aes128gcm-Verschlüsselung)Nötige Konfiguration (nicht im Code — Secrets/Env)
VAPID_PUBLIC_KEY,VAPID_PRIVATE_KEY,VAPID_SUBJECTVITE_VAPID_PUBLIC_KEY(öffentlicher Schlüssel), danach Redeploysupabase functions deploy send-push(MCP-Deploy war in der Session blockiert)Test plan
send-pushdeployedVITE_VAPID_PUBLIC_KEYin Vercel gesetzt + Redeployhttps://claude.ai/code/session_01G1v5ZGvnrS5hb6eX2hfxKb
Generated by Claude Code