I'm not going to lie, I think it's the best feature

Disregard, I've found the problem. In one of my tries to fix the other bug I ended up writing launcher.js rather than loader.js. It's all fine now.

I'm not going to lie, I think it's the best feature

I have a few questions about NodeBB, though I'm quite sure about their answers I'll still ask in case there's some plugin or something I missed.

1. Is there a way to warn users and this show up for all moderators, like when flagging posts?

2. Like the above, can you make an user require post approval? Or even disallow to post? Both for a set time.

3. Can you prevent tag creation?

Disregard, I've found the problem. In one of my tries to fix the other bug I ended up writing launcher.js rather than loader.js. It's all fine now.

I've followed the docs for installing NodeBB on one of our Ubuntu servers.

I've installed Nodejs 6.10.2 - the LTS version - and Redis rather than MongoDB.

Both are working, I can access Redis, read and write on it.

I have two problems, but I'll focus here on systemd. I've created the service file, but it does not work. This is what I get when I check the status:

nodebb.service - NodeBB forum for Node.js.
   Loaded: loaded (/lib/systemd/system/nodebb.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit-hit) since Thu 2017-04-20 00:53:59 EDT; 1h 42min ago
     Docs: http://nodebb.readthedocs.io/en/latest/
  Process: 20405 ExecStart=/usr/bin/node /opt/nodebb/launcher.js --no-daemon --no-silent (code=exited, status=1/FAILURE)
 Main PID: 20405 (code=exited, status=1/FAILURE)

Apr 20 00:53:59 .io systemd[1]: nodebb.service: Unit entered failed state.
Apr 20 00:53:59 .io systemd[1]: nodebb.service: Failed with result 'exit-code'.
Apr 20 00:53:59 .io systemd[1]: nodebb.service: Service hold-off time over, scheduling restart.
Apr 20 00:53:59 .io systemd[1]: Stopped NodeBB forum for Node.js..
Apr 20 00:53:59 .io systemd[1]: nodebb.service: Start request repeated too quickly.
Apr 20 00:53:59 .io systemd[1]: Failed to start NodeBB forum for Node.js..
Apr 20 00:53:59 .io systemd[1]: nodebb.service: Unit entered failed state.
Apr 20 00:53:59 .io systemd[1]: nodebb.service: Failed with result 'start-limit-hit'.

Huuugh, so easy. Thanks a lot, it's working. But now it's time to understand the code.

I'm on Arch and NodeBB is working fine, but I'm having problems when trying to debug it.

I've followed the documentation on how to use node-inspector. While I don't call the kill command I can access NodeBB in localhost:4567 but after doing so it just never loads. Opening node-inspector I can see the files and add breakpoints but I can't load NodeBB.

This is making me so angry that I don't know how I've not given up yet.