Also be aware that it can take some time for nbbpm to take the changes up. I can't remember exactly how long it can take but it is for sure not instantaneous.

@jtsimoes Yes, you could call it an e-mail blacklist.

I'm searching for a possibility to ban the registration with a specific e-mail address or even better would be to ban specific patterns of e-mail addresses. Is this possible with NodeBB? I'm unable to find anything. If not are there any known plugins that can achieve this? So far I wasn't able to find anything.

Thank you in advance!

@baris said in Is there a simple way to analyze long running queries?:

You can temporarily disable all cron jobs and see if the issue goes away, then we can pinpoint which one causes it. If it is still happening then it's not the cronjobs.

Do you mean in code? Or is there actually a setting to disable them all?

@baris One nodebb process is running.

@julian So far I haven't noticed it outside of production. But my development machine is quite different. Also I usually don't have Prometheus attached to my development environment so it might be possible I don't even notice it. I'll have to look into setting up a second environment without any load but otherwise similar to the production environment. Might take me some time

@baris Yes, they are. But further analysis seems to reveal, that is happening much more often and is building up in spikes before it drops again. This is the measurements for an hour:

Those spikes building up are about 1.5 - 2 minutes apart. I missed them previously as I wasn't zoomed in enough. The measurement is done every 15 seconds. I'm pretty sure it has something to do with the change to NodeBB 1.11.x since I hadn't such problems in NodeBB 1.10.x. But I still have absolutely no clue what it is and a very hard time to find possibilities to analyse this better.

I found something new today. First it seems to have gotten quite bad at times. Lag spikes of up to a seconds. The second interesting thing is, that it happens on a schedule. It happens every 25 minutes. Is there anything in NodeBB that is happening every 25 minutes?

@baris said in Is there a simple way to analyze long running queries?:

If you are running mongod, you can try running db.currentOp() to see the running queries during the 503.

Oh, sorry. I might have formulated this a bit misleading. I was more thinking of the HTTP request. Basically find out long running NodeBB requests. I'd like to find out what causes the spike. A long running DB query shouldn't cause a spike as this is IO and shouldn't hurt the NodeJS event loop lag? If there is additional lag there has to be a longer running calculation in NodeBB. Or am I wrong with this assumption?

In NodeBB 1.10.2 I had many 503er and thus decided to just increase the event loop lag threshold to 200ms and also set the check interval to 1000ms. This made most 503er disappear. After upgrading to NodeBB 1.11.2 now suddenly again there is a 503er every 1-5 seconds.

CPU load is not an issue. Memory is also enough available. But I notice that the NodeBB and NodeJS event loop lag at times spikes. And I would like to find out why that is or which queries created those spikes. Is there a possibility to get this information from NodeBB? Are there suitable hooks that could be used for such monitoring?

As far as I'm aware this completely depends on the search plugin you're using.

The url configured in your config.json needs to match the URL by which you want to access the site. So if you want to access the site via https://www.mymainsite.tld/forum you have to set the url in config.json to this value.

I would love to move it. But I'm not sure if it is possible.

Disabling it for global moderator should be possible. I'll have a look at it. There is still several things I'd want to do with this plugin. The name is actually really the target. I just really wanted the mod badges in for the maintenance window I had to upgrade to 1.10.2

There is a widget to display the list of moderators for a category.

To display a mod badge for the moderators in their category I just recently created my own plugin. Be warned that it is in really early alpha and currently mainly focused on my own forum: https://www.npmjs.com/package/nodebb-plugin-user-badges

@PitaJ A custom skin created by me or my community. I know there is the possibility to inject your own CSS. But it doesn't work out will all the skins. So I would love if I could just provide some additional skins by myself. And then let the users decide themselves if they want to use the default skin, one of the Bootswatch skin or the ones created for my forum specifically.

Is there a way to add a skin to the NodeBB Persona theme and make it selectable by the users. Like we already have the possibility for the users to choose the available Bootswatch skins?

Well Ubuntu Server 16.04 is still supported until 2021. NodeJS 8 is an LTS version that is supported until the end of 2019. They might be a bit older, but are well tested and probably more stable than Ubuntu 18.04 and NodeJS 10. Thus it is perfectly up-to-date. But you can do the exact same steps with never versions of Ubuntu and NodeJS.

@gerald-in-korea You can actually own Webstorm. There is a perpetual fallback license: https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-a-perpetual-fallback-license-

But like the others said, Visual Studio Code and Visual Studio 20xx are not the same at all. I'm actually using Visual Studio Code as my general text editor in Linux. Would never do that with any of the Visual Studio 20xx

And yes, Microsoft is horrible at naming their products.

@PitaJ said in Setting up NodeBB with Mongo on Fedora 28:

@Dravere I don't see how your method is functionally any different from just using the user's home directory

Functionality wise there is no difference, but it is more standard conforming as far as I'm aware. Also in theory it might be a bit more secure as I'm creating a system user that by default can't login to the machine. If you're creating a regular user you'll have to disable his login rights separately.

@sweetp In your ACP under Manage -> Privileges. Select a category (not global) and remove create topic privilege from registered users.

@PitaJ But /opt should be the right folder. Creating a new user will need root as well. I usually create a new system user (without home directory) and assign it to the software it needs to run in /opt.

Thus for example install it in /opt/nodebb. Create a new system user, on Debian based systems that would be:

sudo adduser \
    --system \
    --no-create-home \
    --group \
    nodebb

And then assign the folder to this new user: sudo chown nodebb:nodebb -R /opt/nodebb.

Also would be nice to setup a SystemD-Service, which would execute /opt/nodebb/nodebb start|stop as the newly created nodebb user.

Or just go with docker from the start.