Skip to content

Commit

Permalink
Added warning to not expose ABLY_KEY to client code
Browse files Browse the repository at this point in the history
  • Loading branch information
sacOO7 committed Nov 2, 2022
1 parent 0230edd commit 2e46339
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ composer require ably/laravel-broadcaster
BROADCAST_DRIVER=ably
ABLY_KEY=ROOT_API_KEY_COPIED_FROM_ABLY_WEB_DASHBOARD
```
> **Warning** - Do not expose **ABLY_KEY** to client code.
2. Uncomment `BroadcastServiceProvider` in `config/app.php`
<pre>
Expand Down Expand Up @@ -130,7 +131,7 @@ npm run dev

<a name="migrate-pusher-to-ably"></a>
## Migrating from pusher/pusher-compatible broadcasters
- The current Ably broadcaster is fully compatible with the [Pusher](https://laravel.com/docs/9.x/broadcasting#pusher-channels) / [Pusher compatible AblyBroadcaster](https://laravel.com/docs/9.x/broadcasting#ably).
- The current Ably broadcaster is fully compatible with the [pusher](https://laravel.com/docs/9.x/broadcasting#pusher-channels), [old AblyBroadcaster](https://laravel.com/docs/9.x/broadcasting#ably) and [pusher compatible open source broadcasters](https://laravel.com/docs/9.x/broadcasting#open-source-alternatives).
- The only difference is for **Leaving the channel** on client side, you should use [Ably Channel Namespaces](https://ably.com/docs/general/channel-rules-namespaces) conventions.
```js
// public channel
Expand Down

0 comments on commit 2e46339

Please sign in to comment.