Let's keep a list of NodeBB installations here :

If you are running your own NodeBB let us know we will add it to the list!

Just merged the group-chat branch into master, it will be available in our next release which will most likely be 1.0.0.

There are some breaking changes and schema changes in this merge.

The upgrade script will go through all the chat messages and assign them to rooms. This might take a while depending on how many chats messages there are in the system. The upgrade script should show the progress in the console.

For all the changes check out this PR https://github.com/NodeBB/NodeBB/pull/3968/files

barisusakli created this issue in NodeBB/NodeBB

closed Group chat closes #1798 #3968

This NodeBB plugin pulls RSS feeds and creates topics in predefined categories.

https://github.com/barisusakli/nodebb-plugin-rss

To customise options for the parser, please consult the "RSS" page in the administration panel, under the "Plugins" heading.

Installation

npm install nodebb-plugin-rss

Usage

1. Click 'Add Feed'
2. Enter the RSS feed you want to pull
3. Select the category you want to post to
4. Enter tags if you want to tag the posted topics
5. Type in the username you want to post as
6. Select the interval to query the RSS feed
7. Select the timestamp to use for the topic
8. Click Save.

I have run some tests to check the memory usage.

The redis INFO command was reporting 811kb at the beginning since I was running the tests on db1. An empty NodeBB installation starts with roughly 405kb of memory usage.

start 811.44 kb

**Users **
100 users 1.04M diff (254kb) per user = 2.54kb
1000 users 3.61M diff( 2,885kb) per user = 2.885kb
10000 users 29.88M diff( 29,786kb) per user = 2.97kb

Posts (500 chars each)
336 posts 30.71M diff(849kb) per post = 2.52kb
996 posts 32.70M diff(2,887kb) per post = 2.89kb
9995 posts 54.39M diff (25,098kb) per post = 2.51kb

The memory usage per user is roughly 3kbs at 10,000 users. This value goes up as we have other structures that grow as the user count grows.

The memory usage per post is about 2.5kbs per post, keep in mind the posts I created are all 500 characters long.

So for 2,000,000 posts and 400,000 users :

2,000,000 x 2.5kb + 400,000 x 3kb = 5.9gb

So theoretically 6gb should be enough.

Hope that helps.

We recently added a new system group called Global Moderators, this group has access to the moderator tools but can't access the ACP. They can also ban users. We will let this group see banned users and flagged posts as well.

We have assigned some users as global mods on this forum as well https://community.nodebb.org/groups/global-moderators.

If you think we missed someone or you want to be a global mod ask for it here.

NodeBB Plugin Browsing Users

This plugin shows who is currently viewing a topic. This was a core feature that we removed a while ago, now it is back as a plugin

Installation

npm install nodebb-plugin-browsing-users

More info at https://github.com/barisusakli/nodebb-plugin-browsing-users

Notes
Currently only persona supports this, if you want to add it to your custom theme make these changes.

Your best posts

This is just a simple theme based on persona that modifies the topic view with a sidebar.

Here is a screenshot when you are at the top of a topic.

Imgur

And here is one when scrolled down.

Imgur

The sidebar is a bootstrap affix so it is always visible when you scroll down, useful when using infinite scroll as well.

The sidebar also reduces the width of the posts so I find it easier to read compared to long horizontal lines.

Reply, sort by and watch are always visible previously they would go out of screen.

There is a lot more room for browsing user images.

You can install it with npm i nodebb-theme-peace

Just committed https://github.com/NodeBB/NodeBB/commit/7610c11cd1b9de53ce185227ab80f86d55d3bd69, this is a pretty big change even though it's just ~300 lines of code. It changes how we store the main post so that alternative sorting works.

If anyone decides to upgrade please make a backup of your database just incase something goes wrong, I have tested it on this forums dataset and it seemed OK but you never know :). Will do more testing as we get closer to 0.5.0.

There are 3 options to sort oldest to newest, newest to oldest and most votes. The sorting can be changed from a dropdown in the bar below the main post and it is saved as a user setting. The admin can also select a default setting from the ACP.

Let us know if you encouter any bugs.

5 barisusakli committed to NodeBB/NodeBB

closes #450

backup database before upgrade!
upgrade script will take the first post of each topic and set the
`mainPid` property on the topic. then it will remove that pid from the
sorted sets for that topic, this was done to make alternative sorting
work.

added a new sorted set called `tid:<id>:posts:votes` that is used to
sort topic posts by vote count, the original sorted set `tid:<id>:posts`
is used to sort by oldest first or newest first.

the main post is added to the returned posts array on topic load and is
always at the top.
theme changes are minimal just a few new data properties on the posts
and the sorting dropdown.
hopefully didn't miss anything too critical.

Thanks to @Ben-Lubar we now have replies to posts. https://github.com/NodeBB/NodeBB/pull/5050

Right now it only displays one level of replies but you can modify your theme and remove this conditional https://github.com/NodeBB/nodebb-theme-persona/blob/master/templates/partials/topic/post.tpl#L87-Lundefined then you will get nested replies as well.

You can update to master or wait for 1.3.0 to get the feature. It looks like this.

As usual please report any bugs you find on our tracker at github.

BenLubar created this issue in NodeBB/NodeBB

closed Add a sorted set for replies-to-this-post #5050

Try running ./nodebb build and starting.

Yeah I think we still support node 8, at least till Jan 2020.

https://github.com/NodeBB/NodeBB/blob/master/src/prestart.js#L26 need to change toISOString on that line.

If the nodebb app is just exiting with no errors check if your system has enough ram and swap.

I don't think there is one but you can write a plugin using the hook filter:router.page. This hook gets called before the actual topic route handler.

In your plugin you can just do this:

myPlugin.filterRouterPage = function (req, res, next) {
	const myAnnouncementTopicId = 111;
	if (req.params && req.params.topic_id && parseInt(req.params.topic_id, 10) === myAnnouncementTopicId) {
		req.query.sort = 'newest_to_oldest';
	}
	next();
};

Should be possible but I am not sure if mongodb transactions work on standalone servers yet, I think they are only for sharded clusters and replica sets.

In version 4.0, MongoDB supports multi-document transactions on replica sets.

In version 4.2, MongoDB introduces distributed transactions, which adds support for multi-document transactions on sharded clusters and incorporates the existing support for multi-document transactions on replica sets.

To use transactions on MongoDB 4.2 deployments(replica sets and sharded clusters), clients must use MongoDB drivers updated for MongoDB 4.2.

More info here https://docs.mongodb.com/manual/core/transactions/

Redis has multi for transactions so we could aim for something like this in our dbal layer.

const tx = db.transaction();
tx.setObject('user:' + uid, data);
tx.sortedSetAdd('users:joindate', Date.now(), uid);
await tx.exec();

So both commands are executed atomically.

You can fix the counts by running the following query in mongodb for each group that has the wrong member count.

// get number of users
db.objects.count({_key: "group:<replace_with_group_name>:members"});

// update group object
db.objects.update({_key: "group:<replace_with_group_name>"}, {$set: {"memberCount": <replace_with_value_from_previous_query>}});

This is fixed now https://github.com/NodeBB/NodeBB/commit/661a0f506828ec4ef03e3db8508484d1df6977a6

0 barisusakli committed to NodeBB/NodeBB

fix: don't show deleted topics on unread

Thanks for reporting, I will get this fixed before 1.13.0

Makes sense. Please open an issue on our github.