Ok. I understand.

I think it's correct. One of the thing I thought about NodeBB was that a good approach was to use Redis for notification etcetc and Mongo for the rest.

In this case to make a summary:

• install nodebb on Mongo.
• create a Redis instance.
• configure the json file with both mongo and redis references.

If you have some example feel free to share

Do you have some example on how to configure the clustering with mongo @julian ?

@baris mmm I'm using mongo.

I have to configure also redis together with mongo?

There is some more extensive docs about it specific to nodebb?

I found this https://github.com/deedw/mong.socket.io but it is already inside the nodebb packages or I have to install it and then put the configuration inside the nodebb config.json?

I understand the potential risk.

Maybe for an old forum migrating to NodeBB can be useful to merge some account from the admin panel in the case one want to login using social where they use a different email.

Is there a way to enable a Moderator with superpower of editing all the sections, ban users, find user for ip address, see user ip, change user's signature, change user's avatar.

A sort of Sub-Admin user (or if you prefer a Super-Mod:)

What's happen when an already registered user login with a social account?

Is there a way to associate to him another account?

The problem is on the Category cause I have a lot of them.

What about the other issue with the cluster=8?

Ok. The problem was the .collection

> db.stats()
{
    "db" : "nodebb",
    "collections" : 5,
    "objects" : 10950579,
    "avgObjSize" : 559.5723418825617,
    "dataSize" : 6127641136,
    "storageSize" : 7159541760,
    "numExtents" : 28,
    "indexes" : 9,
    "indexSize" : 2563102416,
    "fileSize" : 10666115072,
    "nsSizeMB" : 16,
    "dataFileVersion" : {
            "major" : 4,
            "minor" : 6
    },
    "extentFreeList" : {
            "num" : 0,
            "totalSize" : 0
    },
    "ok" : 1
}

Now I fixed the auth issue, but the problem remains with the command

 > MongoDB shell version: 2.6.5
 connecting to: test
 > use nodebb
 switched to db nodebb
 > db.auth('myuser','mypass')
 1
 > db.collection.totalIndexSize()
 > db.collection.stats()
{ "ok" : 0, "errmsg" : "Collection [nodebb.collection] not found." }

Thanks @baris for your reply.

Now I have 2 issues:

writin db auth I get

2014-11-06T08:28:27.812+0100 ReferenceError: nodebb is not defined

Enabling clustering with cluster=8 cause I have 8 cores NodeBB start having lots of issues.
Options not savings, a message appearing/disappearing continuosly with a reference to unable to connect or similar (I can't read the message cause it's firing too fast.
In the admin there is a spinner running all the time in the nav bar.

If I disable clustering it starts working again.

@baris said:

What kind of load does the server have?

Node is consuming 99% of 1 CPU, but I'm the only user navigating the forum.
It's on a test environment, not production.

Mongodb runs better if all indices fit in ram(http://docs.mongodb.org/manual/tutorial/ensure-indexes-fit-ram/). So make sure your server has enough ram.

24GB of Ram. I think it's enough.

If there are lots of users accessing the forum you can spin up more NodeBB processes using the cluster setting.

Do you have some docs on the cluster settings? This is all https://docs.nodebb.org/en/latest/scaling/?
There's something more?

How many categories and recent replies are you displaying on the home page? The more you display the slower it will get.

I'm using the default settings.
From where I can choose what to display?
I also see that the admin categories panel is very slow.
Doing some shell command from Mongo

[root@gt1 ~]# mongo
MongoDB shell version: 2.6.5
connecting to: test
\> db.collection.totalIndexSize()
\> use nodebb
switched to db nodebb
\> db.collection.totalIndexSize()
\> db.collection.stats()
{
    "ok" : 0,
    "errmsg" : "not authorized on nodebb to execute command { collstats: \"collection\", scale: undefined }",
    "code" : 13
}

I migrated a big forum to nodeBB+mongodb and I'm making some test, but for example I see that the home page is very slow to load and that node process consume a lot of resources.

There are some tuning to do on the mongo side?
Anything to do on the NodeBB side?

I agree that the /category/ slug is not useful at all. Not useful from a Usability perspective and not useful from a SEO perspective.

I think it should be better something like /announcements-1/ or /1/announcements/ or /announcements/1/ without adding the /category/.

And also for topic I don't think there a real utility in adding /topic/ in the URL.

In any case it's a small issue from an SEO perspective.

But why not putting a URL value in the database for the categories to get rid of the id and the /category/ slug?

@a_5mith yes but sometimes you can have structural (core) limitations that prevent some kinds of URL rewrite.
I'd like to know if here we have a case like this or if it's a possible way.

@a_5mith said:

redirects based on your old link structure, you just need to configure it as it's based on UBB.

Yes I saw that, but for a very big forum I'd like to prevent redirecting so I think it would be useful to have a Custom Permastruct option.

I think it would be very useful to allow the admin to choose a permalink structure like:

• default
• /$(category) + /$(category)/$(topic-title)-$(topic-id)
• /$(category) + /$(category)/$(topic-id)-$(topic-title).html
• etc etc....

so it will be easier for old forums to migrate.