How do i install NodeBB

NodeBB Development

Suggested Topics

  • 0 Votes
    3 Posts

    @grabmaier Absolutely, try it out and share with us what you build.

  • 0 Votes
    17 Posts

    @julian and this is enough. Im done with any type of conversation with you.
    In addition to this :: I will not contribute any of my asset (time/code/whatever you think I have) to NodeBB.

  • 0 Votes
    3 Posts

    @pitaj Thanks a lot! Works perfect 💃

  • 1 Votes
    2 Posts

    @ arasbm:

    There's some work being done to dockerize the install. If that doesn't do the trick for you, I expect some of the same automation will.

    NodeBB CentOS Dockerfile

    Typical scaling of NodeBB is multiple processes managed as a cluster by loader.js. Node.js manages its own internal thread pool, so we don't touch threads. H...


    NodeBB Community (

  • 1 Votes
    1 Posts

    Something that interested me when I first started hacking on NodeBB was how the platform uses realtime communication through (and websockets). This interest stems from work I did whilst working as a realtime engineer at Pusher several years ago. One of my research projects whilst there was to look into how websockets get used in production, and other use cases for websockets besides the standard "subscribe to a channel and receive events".

    In 2011, I gave a talk at Keeping It Realtime conference in portland about some of my findings, you can watch it here: (long hair and all) or check out the slides here:

    How NodeBB currently seems to use realtime communication:

    RPC: Request data from the server, get a response back, present that data to the user (or send data to a server like you would POST to a HTTP server) Channels: Used for user to user chat messages Events: Used for online/offline states of users.

    I may have missed something here, so, let me know if I have.

    Most of the websocket usage appears to be in RPC style messages: Get this piece of data do something with it. At present, all realtime communication for NodeBB is built on top of, which uses a protocol more tailored for event type packets, rather than for RPC style packets. For this, something like JSON RPC may be more appropriate.

    Refactoring this deep internal of NodeBB would make the platform more resource efficient on the wire, and also allow for better logging and handling of data. You'd know exactly what has failed on the client-side or server-side and be able to give an appropriate response. In the code, refactoring this level of things would make the code far cleaner, and give option to provide all HTTP Verbs over WebSocket or vica-verse (meaning if you wanted to, you could make 90% of NodeBB standard HTTP. You'd end up with an "api" module internally that is everything that can be exposed, which simple returns back standard javascript objects.

    For user-to-user chat messaging you could still multiplex that onto the same actual websocket / connection (although it's arguable if this is actually beneficial).

    Why do any of this writing or work? Interest more than anything else, but it may make the code to NodeBB cleaner, and improve maintainability.