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.

    805 Topics
    5k Posts
    sameer aroraS

    No in this feature we wish to post comments / message to user profiles. everyone can do that. for example wishing a user happy birthday on there profile.

  • 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
    515 Posts
    julianJ

    There have been some scattered discussions I've seen over the past year that mention that @[email protected]'s WordPress ActivityPub plugin federates their blog posts out as an as:Note, and that the only reason this is done is because Mastodon only treats as:Note (and as:Question) as a first-class object and relegates anything else to a fallback handler that takes a short snippet of the content, and shows a link back to the original source, thus losing any in-app benefits (boosts, replies, etc.)

    Whether this is actually true or not, I do not know. So that's why I'd like to ask Mattias — or anybody else with some context — here.

    For reference:

    as:Article: Represents any kind of multi-paragraph written work. as:Note: Represents a short written work typically less than a single paragraph in length. as:Page: Represents a Web Page.

    I have also noticed that Lemmy, perhaps out of principle, sends out an as:Page for new generated content, and only the replies federate out as as:Note. It has unfortunately led to some assertions that Lemmy's federation is "broken", even though it is arguably not the case.

    @[email protected], care to weigh in?

    I don't even blame Mattias for opting to send everything out as as:Note.

    End of the day right now it doesn't matter how Mattias or Nutomic represent their higher-level collection of data, because Mastodon is the largest implementor and neither they — nor anyone else I know of, for that matter — treat anything that's not as:Note or as:Question specially.

    But that ought to change. The question is how, but this WG is not at the point where we start throwing around decrees and making up standards.

    What's important to me right now is what the landscape looks like right now, and why that is the case.

    N.B. The discussion here will eventually make its way to online real-time discussion at one of the future WG meetings.

  • Help Translate NodeBB
  • Woo new milestone

    2
    0 Votes
    2 Posts
    1k Views
    julianJ

    Thanks @quahfamili! Glad to put a marker on it, even if development is always continuous 🙂

  • Ajaxify

    3
    0 Votes
    3 Posts
    2k Views
    julianJ

    Hey @RefinedSoftware, @caske33,

    There's an ongoing issue right now with plugins not being "ajaxified" in the admin panel. "Ajaxifying" is our pet name for our shorthand method that loads pages in NodeBB (since it is a one-page application, it doesn't truly do a page reload when you click links).

    Give it a try, if you'd like:

    Open up your console (hit F12), and navigate to the console tab, if it is not open already Type in ajaxify.go('users/online') ;

    Also, it looks like I found a bug with the Skype Emoji -- darnit.

  • Test

    1
    0 Votes
    1 Posts
    1k Views

    Amazing forum engine

  • 0 Votes
    2 Posts
    2k Views
    barisB

    Hi @sbdubz, our indiegogo campaign was over in August. We do have some unit tests but they do not cover the whole codebase yet. With that said NodeBB is already pretty stable and we usually get onto bugs that crop up within the same day.

  • Code style

    4
    1 Votes
    4 Posts
    2k Views
    barisB

    I think you are referring to vars like

    Link Preview Image File not found · NodeBB/NodeBB

    Node.js based forum software built for the modern web - File not found · NodeBB/NodeBB

    favicon

    GitHub (github.com)

    If that's the case you are right those can and probably should move into the functions where they are used.

  • User feedback issues

    2
    0 Votes
    2 Posts
    2k Views
    julianJ

    Responded here

  • Setting up a NodeBB forum for dummies

    Moved
    1
    0 Votes
    1 Posts
    3k Views
    julianJ

    Thanks to @psychobunny for the excellent guide!

    Setting up a NodeBB Forum “for Dummies”

  • Prerequisites to development

    5
    1 Votes
    5 Posts
    2k Views
    julianJ

    Heroku allows developers to run small instances for free (even their redis add-on is free), but if your site becomes popular, you will have to pay.

    We have a guide to setting up NodeBB on Heroku in our wiki.

  • Installing NodeBB on joyents smartos solaris

    4
    1 Votes
    4 Posts
    2k Views
    X

    great forum!!

  • upgrade before setup

    3
    0 Votes
    3 Posts
    2k Views

    sdfdsfsdfsdf

    list item

    list item

  • NodeBB v0.0.7 released

    Moved
    4
    0 Votes
    4 Posts
    3k Views
    julianJ

    We saw! Thanks for the write-up 🙂

    The more press the better (Y)

  • Dependency installer on first start

    1
    0 Votes
    1 Posts
    1k Views
    ToyzT

    I was working on my NodeBB server last night and noticed how actually annoying it is to set up, so not anyone can simply set it up...

    So I started to ponder if I can make the process faster and easier for everyone to use and I came up with the following idea which I was able to get working on a NodeBB install integrated right into NodeBB which basically took all the methods and checked.

    So What i did was the actual following:

    Updated App.JS to support require.Resolve() method to check for all needed files Made a basic requirements reader that was able to read the NodeBB package info
    *Made it so it test each module to see if it existed on every start up, checked for updates and updated if needed or downloaded them and installed them if needed

    Doing this took out about 15 to 20 mins of work for a none NodeJS user so all someone know would have to do is basically run

    Node App

    Without needing all the other things such as

    Node install

    Or anything of the sorts, i am working on also making it get it's other needed resources like redis and a few others

    Will Post source to my github when I get home from work

  • My smf to NodeBB migration thread

    10
    5 Votes
    10 Posts
    6k Views
    P

    Hey,

    I'll post some stuff here regarding my migration from SMF 2.x forum to NodeBB. I've had a forum for ~4 years and it's about time I revamped it. I'm a huge node.js and redis fan, so having a forum written in php is blasphemous.

    thanks for all the effort you've put into this!:)

  • Very interesting project

    9
    0 Votes
    9 Posts
    3k Views
    julianJ

    seems like 0.7 to be out soon!!!

    Soon... soon... :S

  • Mobile issues

    2
    1 Votes
    2 Posts
    1k Views
    P

    thanks for the bug reports @quahfamili - please feel free to add issues on our bug tracker here:

    Link Preview Image Issues · NodeBB/NodeBB

    Node.js based forum software built for the modern web - Issues · NodeBB/NodeBB

    favicon

    GitHub (github.com)

    and we'll sort em out as soon as we can - thanks!

  • Longer usernames

    1
    0 Votes
    1 Posts
    1k Views
    I
    Longer Usernames

    I submitted a pull request on the NodeBB github. Check it out!

  • Campaign is over what is next

    3
    0 Votes
    3 Posts
    2k Views
    julianJ

    Hey quahfamili,

    Sorry about the delay -- and thank you very much for your contributions!

    Now that the campaign is over, we don't intend on stopping development. We're aiming to push more stability fixes and aim to be "feature-complete" within the next couple weeks.

    Perks will be fulfilled as soon as possible, although fulfilment of the SaaS hosting perks will have to wait until the SaaS portal itself is up and running.

  • V

    6
    0 Votes
    6 Posts
    2k Views
    julianJ

    I hope you continue working on it. It can be really huge. 🙂

    Thanks! We're really proud of what we've done so far. If there's anything you need, please let us know, and we'll try to accomodate!