@scuzz said in Moving a NodeBB mongo DB from one server to another.:

Once the database has been restored correctly you can run the NodeBB installer.

When it asks for the database you will just tell it the database name of the database you just restored.

This should then install NodeBB with your old database.

Yes, this has worked for me as well.

Making a backup of the nodebb database on the old server, for example:

mongodump -u nodebb -p [password] -d nodebb -o dump/nodebb-2018-03-30

Restoring the nodebb database from that backup, after copying it to the new server:

mongorestore -u nodebb -p [password] -d nodebb dump/nodebb-2018-03-30/nodebb/

And then installing NodeBB on the new server.

When creating a new category, in my opinion spiders should have the same access privileges of guests by default, because in most cases people expect their forums to be public and indexed by Google, etc. They can change the settings when creating a private category.

Looking at the NodeBB data on Open Hub (stats on open source projects), it seems a reliable project with continuing daily work. Congrats on that.

By the way, NodeBB is nearing the 100,000 lines of code soon:

You can also try Solr search for NodeBB.

First install solr-jetty (jetty is lighter and has better performance than tomcat):

sudo apt-get install solr-jetty

(This also automatically installs the many needed dependencies, basically Java packages).

Optional: Temporarily open port 8080 if you want to see Solr admin (not needed):

http://example.com:8080/solr/

(Port 8080 worked for me; if not, try 8983).

Then install NodeBB's Solr plugin:

NodeBB Admin > Extend > Plugins > Find Plugins > nodebb-plugin-solr > Install

Then activate the plugin, restart NodeBB, reload admin page, and go to:

Plugins > Apache Solr

Configuration:

Host: localhost
Port: 8080
Path: /solr

Save Settings

Reload NodeBB and admin page.

Connected

Indexing Enabled

Rebuild Search Index

Disable port 8080 (or 8983) on firewall for security.

It works well.

@a1nb0 Maybe others can help you. I maintain just a couple of sites with Ghost as root and NodeBB in a /community subfolder. The only integration I’m using, apart from the menu links, is the NodeBB plugin for blog comments integration, which I think is currently the only Ghost–NodeBB integration that works out of the box after simple configuration. All the user management on those specific sites is done within NodeBB only.

For other integrations, I don’t know the details, only a few very basic concepts, but probably you would need to do some development work, or at least extensive reading, adaptation, and customization.

For example, for SSO (Single Sign-On) using OAuth 2.0 with oauth2orize for Node.js—since both NodeBB and Ghost are on Node.js—you can study these possibilities:

• NodeBB OAuth SSO (search also for related threads on this forum).
• How does OAuth work with Ghost?

To code other possible integrations, see NodeBB's Write API and Ghost's API.

@meetdilip: If the self-moderation system is abused, a solution could be a settings option to increase the number of users flagging a post to automatically hide it.

@faizanzahid Those in the screenshot are the global privileges. You want to change the category privileges, selecting each category (see up to the right), at least the root ones. There is also a button to copy privileges to the children categories.

@abhinov-singh With a normal configuration, NodeBB needs MongoDB running. You can check it with:

service mongod status

Also, you can try from your nodebb folder:

./nodebb status
./nodebb restart

See also your nodebb/logs/output.log file, or just the recent lines with:

./nodebb log

(Ctrl-C to exit)

@dlooshi

NodeBB Documentation

@abhinov-singh If you are using Nginx on Ubuntu, the configuration files or symlinks (including ports, etc.) are at /etc/nginx/sites-enabled/
See also which ports are left open by your firewalls (server, PC).

Moving a NodeBB mongo DB from one server to another.

@syl said:

the "tag intersection" feature (an URL that lists all topics containing both tag1 and tag2). There is no such feature in nodeBB, am I right?

To get the JSON, we can prepend api/ to the URL. For example, for the tag "plugin" the topic list is:

https://community.nodebb.org/tags/plugin

and the JSON:

https://community.nodebb.org/api/tags/plugin

However, this is for one tag. I don't know if there is a way for more than one.

Related info:

• Rendering Engine - NodeBB Documentation
• NodeBB’s Write API
• nodebb-plugin-blog-comments
• [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget)

@julian Perhaps, instead of “Guest 2839” for a user who deleted the account but not the posts, something like “Former 2839” or similar.

It‘s more respectful than “deleted” for former users that chose to go and weren’t spammers, but on the contrary wrote valuable posts that were kept.

Of course, in the case of spammers, account and posts are all deleted, so no need for “deleted user”.

@The-Worms said:

https://github.com/psychobunny/nodebb-plugin-blog-comments

Work fine

Yes, that’s the official one, and it's working with Ghost 1.x for me as well.

This blog comments plugin is used on the official blog.nodebb.org

See also on this forum: [nodebb-plugin-blog-comments] Blog Commenting Engine (Ghost, Wordpress widget) | NodeBB

@julian said:

This would also cause some topics/posts to be owned by the Guest pseudo-user.

Maybe this could fix it:

It appears now as a Guest's post.
The user's record is gone, but the post's record still contains the user's uid number. So the post could appear attributed to "Guest 2839" instead of only "Guest" for all past accounts.
(Allow users to delete or "close" their accounts · Issue #1284 · NodeBB/NodeBB)

Maybe the stats include bot traffic (search spiders) visiting pages for updates, unless they are filtered. You could compare for example with Google Analytics results.

@aaron-murray Although the Blog Comments plugin is mainly for Ghost and WordPress, it also includes some suggestions for other kinds of sites—on different template engines—in the General section of the Readme.

Not sure for static sites, but they say: “If you don't have such ID, you can use this function that generates a unique ID from the URL”.

@worp1900 said:

On our NodeBB instance, we have a regular (once a month) events, where the highest number of users (~40-80, so not very many) are concurrently online.

That shouldn’t be a problem. See for example this case with an average of 100 concurrent users and working fine on very moderate resources.

However, they use Nginx, which works much better for concurrent users, etc. than Apache.

Anyhow, there is probably some misconfiguration somewhere. To find it by trying different configurations, of course there are many load testing tools to simulate concurrent users. But sorry, I’m just an user with no load testing experience.

If I’m not wrong, looking at the admin panel, it seems this can be done with privileges as well, similarly to that mentioned topic, but for specific private groups and categories:

Admin > Manage > Groups > + > Create Group

Admin > Manage > Privileges > [category instead of global] > Add Group

And set access, etc. privileges for that group of users and private category only.

Then, to add users:

Admin > Manage > Groups > [group for that category] > Edit > Add User to Group

It's possible to also give user-specific privileges such as moderator in the Privileges section. Or probably better using:

Admin > Manage > Admins & Mods > [category] > add-moderator

However, even with moderators, the site admin would need to create the categories and groups, set privileges, etc.

@a1nb0 Maybe others can help you. I maintain just a couple of sites with Ghost as root and NodeBB in a /community subfolder. The only integration I’m using, apart from the menu links, is the NodeBB plugin for blog comments integration, which I think is currently the only Ghost–NodeBB integration that works out of the box after simple configuration. All the user management on those specific sites is done within NodeBB only.

For other integrations, I don’t know the details, only a few very basic concepts, but probably you would need to do some development work, or at least extensive reading, adaptation, and customization.

For example, for SSO (Single Sign-On) using OAuth 2.0 with oauth2orize for Node.js—since both NodeBB and Ghost are on Node.js—you can study these possibilities:

• NodeBB OAuth SSO (search also for related threads on this forum).
• How does OAuth work with Ghost?

To code other possible integrations, see NodeBB's Write API and Ghost's API.