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
With PR #253, we now configure peer-pad to use a rendezvous server running on localhost when the developer runs npm start. If the developer doesn't read the documentation, they might not know that they need to also run npm run start:rendezvous ... if they don't the application prevents editing, and it's not really obvious what is happening.
In #253, we discussed either running the rendezvous server automatically, or indicating to the user that they need to run it themselves.
The text was updated successfully, but these errors were encountered:
what happens is that the binding fails and the node silently fails to start, right?
this in itself is kind of broken (libp2p/js-libp2p-websocket-star#61), you should generally be able to use the app in single-player mode, especially for development, though right now making that happen unfortunately requires fixing js-libp2p
With PR #253, we now configure peer-pad to use a rendezvous server running on localhost when the developer runs
npm start
. If the developer doesn't read the documentation, they might not know that they need to also runnpm run start:rendezvous
... if they don't the application prevents editing, and it's not really obvious what is happening.In #253, we discussed either running the rendezvous server automatically, or indicating to the user that they need to run it themselves.
The text was updated successfully, but these errors were encountered: