Skip to content

NodeBB Development

Stay tuned here to hear more about new releases and features of NodeBB!

3.5k Topics 22.2k Posts

Subcategories


  • Posts from the NodeBB Development Blog
    96 Topics
    778 Posts
    julianJ

    Occasionally, we will get asked whether there are any differences between our hosted service and the open source project.

    It is as though we are holding back some great features and only allowing our paying customers access them! Conversely, it could be assumed that because we are hosting the software for others, that we would somehow out of self-interest or for economic reasons, deliver an inferior version with limitations.

    I'd like to say upfront that this is not the case for NodeBB.

    When you use our hosted service, you receive the same great NodeBB software that you can get for free off of our GitHub repository.

    What we're selling is support, maintenance, upgrades, and peace of mind delivered by our world-class† support team.

    You definitely can host NodeBB on your own! We've strived for years to deliver a piece of software that runs lean and fast on minimal hardware, great docs (some contributed by other admins!) that help you get up to speed quickly, and a fantastic community that will help you if you get stuck.

    The reason I take this principled stand is simple — I think it's unfair when artificial limitations are placed on software just for the purpose of getting customers to pay more.

    We've seen all this time and time again:

    You can't install any plugin you want, just a select few from a small list You can only have X units (tickets, posts, etc) of whatever you're using You can only have X admins/owners You can't see any messages older than X days

    These limitations are all artificial, and serve to restrict the use of something to the bare minimum. Anything extra is — of course — available for the right price.

    We don't do that. We tell everybody that NodeBB is powerful enough to run huge communities, and we stand by it. We tell everybody that NodeBB is flexible enough to look and function however you want, and we stand by it.

    These are the real limitations we impose on our hosting service:

    Hard drive space for uploads are imposed by our upstream provider and are set, though we are happy to add additional drive volumes for a fee) We have soft "pageview" limits that any user on our hosting can exceed (in fact, many do). We set them purely as a benchmark for the point at which your NodeBB may slow down depending on the type of load that you get, and encourage dialogue to make sure that you're on the right plan (server resources, etc.) We do not allow shell access for security reasons (and if you needed it, you probably could self-host)

    So please do rest assured when I and others tell you that what you see is what you get. No more, no less. I'd rather everybody get to use the best of NodeBB, instead of serving a special feature-reduced version for others.

    † I'm going to go out on limb here and say that we're probably the most qualified people to maintain NodeBB. Feel free to disagree 😉

  • You have a cool idea about NodeBB? Post it here.

    806 Topics
    5k Posts
    crazycellsC

    you can find more info here:

    Link Preview Image mute function for users

    It would be nice to have mute function for angry users ... Facebook groups have this, whenever some problem happens (which does not necessarily require a ba...

    favicon

    NodeBB Community (community.nodebb.org)

  • Found a bug? Why not make a bug report here?
    1k Topics
    7k Posts
    serhatS

    11dad6df-40c2-48ce-8aa2-cf26919c7ab3-image.png

    I successfully installed NodeBB using docker-compose.

    Everything seems to be working as expected, but when the nodebb container starts up, NodeBB starts running. However, when I connect to bash and check its status using the CLI, it shows that NodeBB is not running, even though it actually is.

    When I try to stop it, I can't. And when I try to start it using the CLI, even though I initially installed it with MongoDB, it gives an error related to postgres.

    Note:
    Initially I've installed NodeBB with Postgres, then I removed the container and installed with Mongo.

    1c23091b-3ef0-46ac-96b5-6145ef19e65c-image.png

  • Focused discussion related to ActivityPub integration in NodeBB

    45 Topics
    548 Posts
    julianJ

    @crazycells it may, it may not, nobody knows exactly how search engines rank sites 😞

  • Help Translate NodeBB
  • REDIS BACKUP

    6
    0 Votes
    6 Posts
    3k Views
    G

    @psychobunny ok just modified the script, thank you!

  • Meet the dev's Q&A

    Moved
    3
    0 Votes
    3 Posts
    3k Views
    ?

    This idea sounds great. Then if you do a successful reddit AMA (We make the sleekest new forum software around...AMA!), you'll get all the nerds.

  • What is this magic...

    10
    0 Votes
    10 Posts
    3k Views
    T

    @Giorgio-Chiodi No problem.

  • A note re: updating NodeBB

    4
    4 Votes
    4 Posts
    1k Views
    T

    @Giorgio-Chiodi said:

    @trevor me?

    The conversation regarding blockquotes has been forked and continued here:
    https://community.nodebb.org/topic/1506/what-is-this-magic

  • 0 Votes
    6 Posts
    2k Views
    B

    Link Preview Image captcha support by akhoury · Pull Request #1533 · NodeBB/NodeBB

    added a new filter:register.build that allows adding a data.captcha html value to the register template data, also made its response add an ?error=message param to the /register url modified hook filter:register.check arguments added few utils functions, check them out, they're cool minor other fixes

    favicon

    GitHub (github.com)

  • [Solved] Where is {topics.category.title}

    2
    0 Votes
    2 Posts
    1k Views
    G

    @julian told me it's actually

    {topics.category.name}
  • [solved] Post title in recent posts

    5
    0 Votes
    5 Posts
    2k Views
    G

    thanks guys! this is the correct one

    posts[i].topic.title
  • NodeBB's Next Theme

    Moved
    33
    2 Votes
    33 Posts
    25k Views
    H

    Will there be a new theme for version .5?

    Just curious (from an excitement for the next version standpoint). The current themes are already leaps and bounds better than other forum scripts.

  • Disable one plugin? New, for v0.5.0

    3
    2 Votes
    3 Posts
    2k Views
    julianJ

    Haha yeah, ./nodebb reset plugin="pluginname" is already in -- would prefer a nicer syntax, so maybe we can introduce the ./nodebb disable command. Unsure atm.

  • [AWESOMENESS] #Hashtags

    4
    0 Votes
    4 Posts
    1k Views
    ?

    Go tags go!

  • [HELP] categories User permissions

    6
    0 Votes
    6 Posts
    2k Views
    julianJ

    👍 Glad to hear it. #933 for latest updates.

  • {topics.posts.content}

    7
    0 Votes
    7 Posts
    2k Views
    T

    @psychobunny said:

    Thanks for answering this @trevor 🙂

    :squirrel: It had my name written all over it.

  • Menu - Where to edit?

    Moved
    6
    0 Votes
    6 Posts
    4k Views
    P

    This one's part of a larger problem, which will be fixed at #1481

    Something that's on my TODO list this week 🙂 In a nutshell, the end result is that we'll be able to define and re-order routes in the ACP.

  • Whooooo wants WYSIWYG?

    20
    9 Votes
    20 Posts
    8k Views
    ?

    This would be awesome to have implemented as an option. Most of my target audience are used to typical BBCode. While several would love Markdown, it will be like a second language to most.

  • Port 80

    3
    0 Votes
    3 Posts
    1k Views
    XiphX

    @jk4321 said:

    If I set the port to 80 in config.json, we get no response at all.

    It might be the case that another process is already listening on port 80. Many popular Linux distributions come with httpd (AKA: Apache) installed and enabled by default, so you could check if that or any other webservers (i.e. Nginx, Litespeed) are running.

    If it's none of those processes, try doing a quick google search for "(name of your OS) port usage".

  • Nodebb partitioning code

    1
    0 Votes
    1 Posts
    811 Views
    V

    I'll work in my research with 'late distribution'. This is a term adopted by me rs. It means that I need to split the code to work in multiple clouds. For example, the 'module' topics would be deployed in Amazon EC2 to use the load balance and the rest of nodebb code in GAE, implementing some communication between the code on the EC2 and GAE. Some ideas?

  • Plugin Listing at ACP

    2
    0 Votes
    2 Posts
    1k Views
    barisB

    Right now it doesn't. @psychobunny is doing some work on the package manager. You can check out the discussion here. Eventually that list will display only compatible plugins with other useful info.

  • Scheduled downtime for our community

    Moved
    12
    1 Votes
    12 Posts
    6k Views
    P

    Lavish. 😁

  • NodeBB Documentation

    Moved
    3
    0 Votes
    3 Posts
    5k Views
    P

    Yeah I gotcha, I know exactly what you mean. It's something we'll think about eventually (traditional documentation generated from comments within source) but moving to repo is a step in that direction I would imagine.

    And thanks 🙂

    yeah will update the link tomorrow 🙂

  • Coffee core

    13
    0 Votes
    13 Posts
    4k Views
    P

    it can be written in teawith2sugars for all the difference it makes

    I prefer my tea black to be honest

    @psychobunny you'll not be able to discourage me through such little issues

    hehe 😉