SOLVED
Added
socket.io {"address": */*};Default "address:" **; that's is problem.
I have a question, how to set up, so that nodebb can interact with the redis socket?
Not sure we've ever tried that -- any particular reason why you want to use a unix socket and not port?
@julian because sockets is fastes
redis.conf
port 0
unixsocket /sockets/redis.sock
unixsocketperm 777
nodebb config.json
"redis": {
"port": "/sockets/redis.sock",
"host": "",
"database": 0
}
@smartpunter for security set perm to unixsocketperm 775
, not 777
@youhosi bad advice, as number of applications under different users may/will communicate with database
Yes, you might want to add all of them to the same group and set proper permissions etc... But those who are able to do this - will do, others can use 777 on file in directory unaccessible from outside.
@smartpunter In that case, add them to the appropriate group: D
@youhosi said in Redis socket:
@julian because sockets is fastes
Faster, less overhead, more reliable. I agree. Although I would not recommend Redis here