SocketCluster / SocketCluster/socketcluster-server

socketcluster-server + sc-broker-cluster

Open
#37 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
109
Forks
49
PR merge metrics
No merged PRs in 30d

Description

Hello,

Could it be possible to get some information or guidance on how to implement the sc-broker-cluster with the socketcluster-server ?

When I set the brokerEngine to 'sc-broker-cluster' in the options I'm getting the following error :

/tmp/scc/app/node_modules/socketcluster-server/scserver.js:101
  this.brokerEngine.once('ready', function () {
                    ^
TypeError: this.brokerEngine.once is not a function
    at new SCServer (/tmp/scc/app/node_modules/socketcluster-server/scserver.js:101:21)
    at Object.module.exports.attach (/tmp/scc/app/node_modules/socketcluster-server/index.js:65:29)
    at Object.<anonymous> (/tmp/scc/app/server:15:36)
    at Module._compile (internal/modules/cjs/loader.js:702:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:744:10)
    at startup (internal/bootstrap/node.js:240:19)```


Thanks !

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the brokerEngine setup in scserver.js around line 101 and the attach path in index.js around line 65, then compare it with the server configuration at server line 15. Reproduce the TypeError with sc-broker-cluster and determine what integration guidance or documented configuration is missing; done means the setup is explained clearly or the reported incompatibility is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
backend
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.