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

FAQ: custom signaling server #1106

Merged
merged 1 commit into from
Nov 23, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -379,18 +379,13 @@ A way to mitigate this in Chrome, is to run your IPFS node inside a Service Work

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

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:
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:

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


```JavaScript
const node = new IPFS({
repo: 'your-repo-path',
EXPERIMENTAL: {
pubsub: true,
},
config: {
Addresses: {
Swarm: [
Expand Down