fix(ops): send apikey with push drain, read the web push public key from release/, record 2026-11-17 backlog evidence
The scheduled push drain got HTTP 401 because modern Supabase service keys need the apikey header next to Bearer. NAS deploy scripts fall back to release/webpush-vapid-public.key (public key only). Map, mobile SSOT and deployment runbooks are synced with the verified operations run in docs/evidence/2026-11-17-backlog-operations.md.
This commit is contained in:
parent
8d8aaf5794
commit
6791e29f27
16 changed files with 254 additions and 96 deletions
|
|
@ -77,6 +77,7 @@ WEBPUSH_VAPID_PRIVATE_KEY=
|
|||
WEBPUSH_SUBJECT=
|
||||
# Browser bundle copy of the same public key. This is public by design and must
|
||||
# match WEBPUSH_VAPID_PUBLIC_KEY; never expose the private key as NEXT_PUBLIC_*.
|
||||
# If blank, NAS deploy scripts read release/webpush-vapid-public.key.
|
||||
NEXT_PUBLIC_VAPID_PUBLIC_KEY=
|
||||
# Apple Push Notification service transport (Firebase-free). Token-based .p8 auth.
|
||||
APNS_KEY_ID=
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue