I've launched my forum recently, plenty of work to do, but hopefully a good start: https://wewin.ru/

Yeah, so run 8 workers and they all will serve requests. That's how nodejs works.

in nginx create records like this (i have 2 cores, so i am running 2 workers:

upstream nodebb {
  ip_hash;
  server unix:/sockets/nodebb.sock;
  server unix:/sockets/nodebb.1.sock;
}

and then in "location" just use

proxy_pass http://nodebb;

Innodebb config json you can set several ports/sockets (sockets in my example, as they are way better and safe, then ports, just take care aboout proper access rights)

"port": ["/sockets/nodebb.sock", "/sockets/nodebb.1.sock"],

Voila, your nodebb installation uses all cores.

@youhosi said in [nodebb-theme-oxide] Oxide Style! 3.0.26:

I do not have this problem.

i have compared this part of code... This one from persona recent.tpl

<!-- IF loggedIn -->
<button component="category/post" id="new_topic" class="btn btn-primary">[[category:new_topic_button]]</button>
<!-- ELSE -->
<a component="category/post/guest" href="{config.relative_path}/login" class="btn btn-primary">[[category:guest-login-post]]</a>
<!-- ENDIF loggedIn -->

This one from oxide

<!-- IF canPost -->
<button component="category/post" id="new_topic" class="btn btn-primary">[[category:new_topic_button]]</button>
<!-- ELSE -->
<a component="category/post/guest" href="{config.relative_path}/login" class="btn btn-primary">[[category:guest-login-post]]</a>
<!-- ENDIF canPost -->

Maybe you should use loggedIn condition instead of canPost? Or it might be a bug in 'canPost' variable calculations... I would go with safer one, because you are showing 'guest-login-post' button and it doesn't connected with ability to post messages. So probably you should use "loggedIn" variable in all parts of code like this (recent.tpl and popular.tpl).

redis.conf

port 0
unixsocket /sockets/redis.sock
unixsocketperm 777

nodebb config.json

"redis": {
  "port": "/sockets/redis.sock",
  "host": "",
  "database": 0
}