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:
Yun Chan 2026-11-20 15:16:19 +09:00
parent 8d8aaf5794
commit 6791e29f27
16 changed files with 254 additions and 96 deletions

View file

@ -81,6 +81,9 @@ if [ -z "${NEXT_PUBLIC_PAYPLE_CLIENT_KEY:-}" ]; then
echo -e "${YELLOW}NEXT_PUBLIC_PAYPLE_CLIENT_KEY is empty: Payple checkout will be disabled in the web app.${NC}"
fi
WEB_VAPID_PUBLIC_KEY="${NEXT_PUBLIC_VAPID_PUBLIC_KEY:-${WEBPUSH_VAPID_PUBLIC_KEY:-}}"
if [ -z "$WEB_VAPID_PUBLIC_KEY" ] && [ -f "$ROOT_DIR/release/webpush-vapid-public.key" ]; then
IFS= read -r WEB_VAPID_PUBLIC_KEY < "$ROOT_DIR/release/webpush-vapid-public.key"
fi
if [ -z "$WEB_VAPID_PUBLIC_KEY" ]; then
echo -e "${YELLOW}NEXT_PUBLIC_VAPID_PUBLIC_KEY is empty: browser notifications will stay unavailable and fail closed.${NC}"
fi