NodeBB Architecture?

Moved Technical Support
  • I had some ideas for NodeBB that I wanted to try and develop. Are there any architecture notes? Any pull requests/issues or comments that dive into how everything works together?

    Thanks!

  • This post is deleted!
  • This requires investment. If the nodebb team had found investors for at least 10 million, the discourse would have fainted

  • @volanar I'm not sure I follow. It seems to be that having notes for how everything works would make development and contribution easier.

  • @nbb123 Hey there! Best bet would be to take a look at our documentation, especially the "development" section — on how to write plugins/themes/etc.

    What exactly are you trying to accomplish? All of the NodeBB team are on the forum, and can answer any technical questions you may have 🙂

  • @volanar That may be true, but we're a different kind of company than those silicon valley startups that raise money. This is not to say that they're bad and we're good — just that we're different in how we approach money.

    They certainly can use that money to do cool things, but at a burn rate that far exceeds ours. We hit profitability organically, by growing our revenue through our SaaS offering and by taking on custom work.

    I like to think we do cool things too, but the downside is I don't have unlimited funds to throw talented developers at every problem that strikes my fancy 🙂

    Maybe someday!

  • @julian said in NodeBB Architecture?:

    I like to think we do cool things too, but the downside is I don't have unlimited funds to throw talented developers at every problem that strikes my fancy

    Unfettered indulgement of fancies tends to lead to gluttonous behavior and feature bloat. The
    "Unix Way" versus the "MS Monolith" approach. Got to take the best from each pray you hit the sweet spot. 👍 🐕

    Otherwise.. Not.... 👿

  • @julian said in NodeBB Architecture?:

    @volanar That may be true, but we're a different kind of company than those silicon valley startups that raise money. This is not to say that they're bad and we're good — just that we're different in how we approach money.

    They certainly can use that money to do cool things, but at a burn rate that far exceeds ours. We hit profitability organically, by growing our revenue through our SaaS offering and by taking on custom work.

    I like to think we do cool things too, but the downside is I don't have unlimited funds to throw talented developers at every problem that strikes my fancy 🙂

    Maybe someday!

    I understand you, but we do not live in an isolated world. We have competition here. And everything needs resources. When choosing a community platform, support is the deciding factor, not programming language. This is the foundation of the foundations, support, support. Support! All modules must be supported. But you have a small team. There are two ways. Finding an investment that suits your history is no problem. You can raise tens of millions and improve your platform to the skies) Or let the community donate to these things. I want to donate hundreds of dollars, but I don't want to take your SAAS. You see who communicates in the community. Basically, these are the owners of individual platforms. They are willing to pay money for support.
    I'm even willing to develop this theme for free, as long as you improve your support. Otherwise, my community is at risk. We just can't stand the competition. By your actions, you are advertising discourse. Writing code is not the main thing, the main thing is support. All modules that are written. There lies success. Create an opencollective account, hire developers and take nodebb to the next level. Otherwise, all your clients will sooner or later go into discourse, there are no problems with this.

  • julianJ julian moved this topic from NodeBB Development on

Suggested Topics


  • 0 Votes
    2 Posts
    47 Views

    @f10w said in Migrating to NodeBB from IP.Board 3.4.9:

    I am rather surprised to find no official guide on how to migrate from another software (e.g., Xenforo, IPS, vBulletin) to NodeBB.

    Unfortunately, one doesn't exist - see below

    Import data from IPBoard

    @julian thanks, @kamov emailed me, I'll update back here if I end up writing the IPBoard exporter.

    favicon

    NodeBB Community (community.nodebb.org)

  • 1 Votes
    2 Posts
    234 Views

    @nguyễn-bảo hey there, can you reach out to us at [email protected] so we can take a look?

  • 0 Votes
    1 Posts
    155 Views

    I've had nodebb setup for a bit now and through some bumps and scrapes have always kept it running. After upgrading to V1.13.0 NodeBB would fail to load with a "Internal Server Error". After updating to 1.13.1 the website once again loads, however when trying to view any topics in the forums it times out loading. I've reviewed every possible plugin that could potentially be in the way and disabled several without success. I'm not seeing anything in the logs so may be looking in the wrong place. Everything is fully functional to posting new topics, viewing recent ones, discarding, deleting, purging, and the admin console. The only issue comes when its time to actually open a topic fully. The RSS Feeds properly display all the recent topics and content as well.

    My server is running MongoDB and proxied via nginx behind LetsEncrypt SSL Certificate, and can be seen at www.zultyscp.com however does require a login, there is a single public post informing Guests that a login is required where you can see the issue.

    Any help on where to look for this and assistance in resolving would be appreciated.

  • 0 Votes
    8 Posts
    1k Views

    Try removing the port from the url.

    And if you are using a domain name, set it to the www.example.com version, as in:

    "url" : "http:www.example.com",

    (Within the config.json file in nodebb.)

  • How To Unbind NodeBB?

    Technical Support
    0 Votes
    2 Posts
    1k Views

    You'll want to find the pid (process id) of the running NodeBB process. Use ps aux | grep node to see all process that are node based.

    Then kill it by pid.

    e.g.

    julian@laptop ~/nothingtoseehere (master) $ ps aux | grep node julian 11381 5.5 1.3 959772 53680 ? Ssl 18:25 0:00 /home/julian/.nvm/versions/node/v4.4.0/bin/node /home/julian/nothingtoseehere/loader.js julian 11396 3.7 0.9 910404 37308 pts/5 Sl+ 18:25 0:00 node ./nodebb log julian 11405 44.0 3.8 1303708 153892 ? Rl 18:25 0:05 /home/julian/.nvm/versions/node/v4.4.0/bin/node app.js julian 11483 0.0 0.0 15192 2260 pts/6 S+ 18:25 0:00 grep --color=auto node

    Looks like the NodeBB app is on pid 11405, and the loader is 11381. kill 11381 will kill both (as the app is a child of the loader)