Community

@teh_g Have your reporter try using the chat page vs the chat modal... ideally the modal should only ever be used on desktop (though I don't think we've made the transition yet)

From a development standpoint it is superior. Yarn works great with linked modules, and is backed by a fantastic team (with corporate backing from some major players as well).

npm tends to clobber all of my linked modules sigh.

Glad to hear your NodeBBs are rockin' 😉

Cyberian.pk
a11adac4-f118-4ba4-858c-f49c0228fb74-image.png
nodebb.com
09a9b011-a660-499e-8b79-fed209e2c44e-image.png

@julian I will admit that I changed the thresholds for the 503 errors a while ago because they were happening a ton...

0_1504066715468_4d769fb7-fd00-444b-91f6-3144667a99c7-image.png

Looks like pagination is broken in 1.5.0? A few of my users reported issues, but I can't even enable pagination on my forums.

See these issues on Github:
https://github.com/NodeBB/NodeBB/issues/5685
https://github.com/NodeBB/NodeBB/issues/5686

@julian It does under v1.4.5. I haven't upgraded to v1.5.0 yet.

@PitaJ v1.4.4

0_1490633559949_upload-031effbd-bc0a-4b32-8061-181db8d412f8

I managed to fix it by deleting my packages.json file, replacing it with the version in github, then running npm install --production

@julian said in clustering on one cpu:

@teh_g Keep in mind that the 503 threshold is conservative, it is likely okay for you to raise that number by a bit before having to spin up new servers.

We did that too, helped a lot.

@julian Any updates on nodebb's CSP implementation? I'd like to avoid unsafe-* for obvious reasons.

You pass in --no-daemon and --no-silent because Upstart works best if the program itself is run interactively, with output sent to stdout.

However, I don't recall if systemd is different...

If it works best run interactively, use --no-daemon.

If it reads output from stdout (which I believe it does), then use --no-silent.

For some reason, my mentions aren't quite working right. When I type the @ symbol, the majority of the time the pick list for the mentions does not open up. It looks like the pick list doesn't open for me whenever the @ is typed on the first line (basically before any line break).

As an example, here is what it ends up looking like:
0_1482349966717_upload-744b25e2-2e44-461d-a9da-9ebd2676debd

A few of my users are reporting that the pick list opens, but closes after one character being typed.

I am using Chrome x64 (latest). NodeBB is up at 1.4.1. No errors in the Chrome console either.
0_1482350174215_upload-42e17644-9295-44bc-93d2-ba46b48d3717

Edit: And of course, after typing this, I also see the issue with the pick list closing after typing one character.

@julian said in notification of downtime:

Bit of a secret undocumented route here... but you can have your uptime robot ping /sping to check NodeBB directly 😄

That is great! I assume if it switches to something other than healthy it is not healthy 😉

@teh_g have you tried installing it via npm?

@baris Thanks! I may pull down that change, I feel so weird not having my favicon.

You should make it 50px, and vertically center the text in the image.

@julian said in site logo not uploading to /uploads/system:

Agreed, that sounds like a prudent course of action.

Done:
https://github.com/barisusakli/nodebb-plugin-imgur/issues/29

Nope. You would need to make a plugin. There's no way to add any additional data to the post without writing your own functions to handle the submit action.

@julian So far so good. I was actually worried since the upgrade was really easy...