You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-6Lines changed: 21 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,24 +70,39 @@ There are several good examples and tutorials on the web:
70
70
* Google's [introduction to push notifications](https://developers.google.com/web/fundamentals/getting-started/push-notifications/) (as of 03-20-2016, it doesn't mention notifications with payload)
71
71
* you may want to take a look at my own implementation: [sw.js](https://github.com/Minishlink/physbook/blob/2ed8b9a8a217446c9747e9191a50d6312651125d/web/service-worker.js) and [app.js](https://github.com/Minishlink/physbook/blob/d6855ca8f485556ab2ee5c047688fbf745367045/app/Resources/public/js/app.js)
72
72
73
-
### GCM servers notes (Chrome)
74
-
For compatibility reasons, this library detects if the server is a GCM server and appropriately sends the notification.
73
+
### Authentication
74
+
Browsers need to verify your identity. A standard called VAPID can authenticate you for all browsers. You'll need to create and provide a public and private key for your server.
75
75
76
-
You will need to specify your GCM api key when instantiating WebPush:
76
+
You can specify your authentication details when instantiating WebPush. The keys can be passed directly, or you can load a PEM file or its content:
0 commit comments