SocketCluster / SocketCluster/socketcluster
is it possible to --inspect-workers and bind to 0.0.0.0 for remote debugging?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Looking here I'm led to believe that I can specify the port, but not bind to allow external connections (maybe?). I've tried to connect to mydomain.com:5859 but chromes remote debugger never picks anything up. Is there something else I need to do?
I'm using Dokku to host my application on a server, so if it should allow external connections, it's possible some proxying is needed? This is my current line of investigation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with index.js around lines 654-661 and trace how --inspect-workers configures the debugger endpoint. Check whether the endpoint host can be configured for external connections, then verify the behavior through the Dokku deployment and Chrome remote debugger. Done means documenting or implementing a working remote connection path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100