Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Commit 1c8ad75

Browse files
AquiGorkadaviddias
authored andcommittedNov 23, 2017
docs(FAQ): fix signaling server description (#1106)
License: MIT Signed-off-by: Jorge Ludlow <gorka@aquigorka.com>
1 parent 0258759 commit 1c8ad75

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed
 

‎README.md

+1-6
Original file line numberDiff line numberDiff line change
@@ -379,18 +379,13 @@ A way to mitigate this in Chrome, is to run your IPFS node inside a Service Work
379379

380380
#### How can I configure an IPFS node to use a custom `signaling server`?
381381

382-
You'll need to execute a compatible `signaling server` ([libp2p-webrtc-star](https://github.com/libp2p/js-libp2p-webrtc-star) works) and to setup the correct configurations params for your IPFS node:
382+
You'll need to execute a compatible `signaling server` ([libp2p-webrtc-star](https://github.com/libp2p/js-libp2p-webrtc-star) works) and include the correct configuration param for your IPFS node:
383383

384-
- enable `pubsub`
385384
- provide the [`multiaddr`](https://github.com/multiformats/multiaddr) for the `signaling server`
386385

387-
388386
```JavaScript
389387
const node = new IPFS({
390388
repo: 'your-repo-path',
391-
EXPERIMENTAL: {
392-
pubsub: true,
393-
},
394389
config: {
395390
Addresses: {
396391
Swarm: [

0 commit comments

Comments
 (0)
This repository has been archived.