Browser notifications #693

[robertrosman]

Added a plugin for browser notifications. Should be pretty straight forward, but a few notes.

1. You need to generate vapid keys and add to the .env file. I added some notes in dotenv.example about how to generate and a warning not to change them once you go live.
2. The service-worker.js script is served as a web view in order to access it at the root level (/service-worker.js). This is required by design of service workers, otherwise it will fail due to insufficient permissions/scope.
3. I haven't really had the change to test it on mobile, since web push notifications only work with ssl encryption enabled (don't even think self signed certificates will work), and I haven't set it up locally.
4. Every device needs to allow notifications individually, and there are some edge cases when denying notification that I've tried to demonstrate in the showcase.
5. My recording software insisted to enable "Do not disturb" mode, by default the notifications should popup without interaction.

Link to showcase

[kennethjiang]

Thank you so much for the PR. I was hoping that I could get it merged soon. But have been very swamped with a few big changes. I will come back to your PR later this month. Sorry about that!

[robertrosman]

No problem @kennethjiang! You're doing a great job, keep it up 👍

[kennethjiang]

Sorry again for the delay. Finally got a chance to try it today. I set .env as:

DEBUG=False
VAPID_PUBLIC_KEY=BNeav6iVhFmO6MxS7gOJO...TDtE
VAPID_PRIVATE_KEY=cLUg_s...YFrkwRI
[email protected]

But when I launched the server, I saw this on the preference page:

So no webpush section is shown. Did I miss a step?