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:

GitHub - psychobunny/nodebb-plugin-blog-comments: Lets NodeBB act as a comments engine/widget for your blog

Lets NodeBB act as a comments engine/widget for your blog - psychobunny/nodebb-plugin-blog-comments

GitHub (github.com)

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.

@a1nb0 The full memberships and subscriptions feature is tagged as planned, although the Ghost team says no ETAs or roadmaps.

@a1nb0 That plugin is just for Ghost–NodeBB comment integration (or WordPress–NodeBB; there is also another plugin for PencilBlue–NodeBB comments).

The other features (register, follow) are within NodeBB, currently not connected to Ghost’s Subscribers feature, which is in beta but working now. They plan to add full membership support to Ghost in the near future.

There are NodeBB OAuth plugins as well, such as the official generic one, nodebb-plugin-sso-oauth, but I’ve not tried those yet for Ghost, just the SSO plugins for Facebook and Google fast register/login (nodebb-plugin-sso-twitter needs an update for Twitter's new SSO policy, that provides user's email address now).

For example, the NodeBB’s official site uses Ghost for the NodeBB Development Blog, as a subdomain linked from the menu of NodeBB’s home page. It also uses the comment integration plugin mentioned by PitaJ.

I think that, excepting for users starting their own blogs, the other features you mention are possible within NodeBB, but the only current NodeBB-Ghost integration that I know of is the one mentioned for comments.

Ghost can be the root site as well, with NodeBB as a linked subdomain or subfolder.

@renaissance said:

Spanish translation of NodeBB is 100% finished and ready to deploy!!!

Thank you very much!

@atayz said:

Yet the dbsearch doesn't support non-Roman alphabet languages for some reason

You can try the NodeBB plugin for Solr search (open source), that supports a large number of languages, including Chinese, Japanese, Arabic, etc. See step by step details.

A website operator can store certain personal data relating to visitors of the site if it helps to identify the visitor and also to protect itself against cyber attacks, the EU's top court ruled on Thursday.
(Websites can store IP Addresses, rules European Union Court, 20 Oct. 2016)

On GDPR (General Data Protection Regulation 2016/679):

It was adopted on 14 April 2016, and after a two-year transition period, became enforceable on 25 May 2018.

@pummelchen said in How to Load Balance for all CPU Cores:

worker_processes

Thanks, that's interesting. They say "It is common practice to run 1 worker process per core." (How To Optimize Nginx Configuration | DigitalOcean).

@atayz said:

Sadly, solr doesn't work for me

Just in case you maybe didn't, remember to install Solr itself as well on your VPS, not just the plugin. I wrote some step by step details recently.

@atayz said in The future of Nodebb:

a multi-language search(non-roman alphabet)?

Apache Solr search supports a large number of languages.
Excellent NodeBB's Solr integration by Julian: nodebb-plugin-solr.

@shiroan-hyun said in Nodebb on my linux:

That's it, I come across this on freenom, then I have some indications?

What Whimpers explained is correct.

Heroku is free ?

Heroku's free plan is limited and just for testing and development, because it "sleeps after 30 mins of inactivity". On the other hand, you can use the already mentioned free months offered by NodeBB at DigitalOcean for a live site.