fix(notifications): drop the unreachable WEB_PUSH_* VAPID aliases

Six WEB_PUSH_* names and NEXT_PUBLIC_VAPID_PUBLIC_KEY sat behind the three
real VAPID_* variables in the env fallback. None was ever on the compose
environment: whitelist and none appeared in .env.example, .env.production.example
or the env manifest, so under the bundled stack a value set under any of them
could not reach the process. Remove them and the self-hosting note that
advertised them.
This commit is contained in:
Marc-André Bombeck committed 2026-09-03 02:12:44 +02:00
1 parent 214b268b41
commit 98597232f2
2 files changed
+16 -17

No files matched your search

+2 -4
View File
@@ -91,10 +91,8 @@ VAPID_PRIVATE_KEY="...(private key)"
VAPID_SUBJECT="mailto:you@example.com"
```
The database values win when both are present. The loader also accepts a
few aliases (`WEB_PUSH_VAPID_PUBLIC_KEY`, `WEB_PUSH_PUBLIC_KEY`, and the
private/subject equivalents) so a config copied from another deployment
keeps working.
The database values win when both are present. These three names are the
only ones the loader reads.
### 3. Subscribe a device