NodeBB Development

@alberto__segura said in Chat REST API endpoint changes: Also, I don't like the admins could directly read other users conversations It was removed and code moved to a plugin. So, admins can read other users conversations if the plugin is installed.

@zoharm said in NodeJS Cluster: Just one more question if possible, wouldn't the adapter also take care of telling all other processes subscribed to the same adapter to emit a message (and thus to all clients connected to those processes?) Ala: To citate: "enables you to send messages between different processes running socket.io all using this same adapter.". So yes, this is basically the whole functionality of that adapter. They will fetch messages from the central storage and send them to the target, if the target is connected to them. Or in case of groups ("rooms"), send it to all in that group connected to them.

@PitaJ said in varnish config: @sanatisharif where is this from? @julian said in varnish config: Might be from our docs... @trevor wrote one up awhile back, so it probably needs some tweaking. https://docs.nodebb.org/en/latest/configuring/proxies/varnish.html

for getting rid of them

Bad gateway might occur due to an incorrect setting in your Proxy. It is recommended by me to use Nginx as it is easy to setup and apparently automatically recovers after a bad gateway. What Operating System Are you using?

@TheBronx I do agree you very much that the polling requests are causing an enormous load on the server. My machine is powerful enough holding 65000+user and 140000+ posts. But the load is heavy at peak time, and if I restart nodebb, it can not even recover until the peak was passed. @administrators Any idea on this? I was obsessed with this for long... I found that the ESTABLISHED connections are too large. Does that count for this issue? No matter peak time or valley time, this number almost seems the same. user@discuss:~$ netstat -n | grep -c ESTABLISHED 14003 and the ulimit: user@discuss:~$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63711 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 10000 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 63711 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited

@faianca using the latest NodeBB version. Redis 3.2.4 Avg. amount of connections (ss -s): ~2000 Avg. amount of people online (forum only): ~120 Avg. load time (without ads): <500ms Avg. amount of pageviews (monthly): ~1.5 Mio. As you can see benchmarks do not mean a damn. I run a dedicated server (self built) at the Illiad Group (France). The websites themselves are split into several smaller VMs by using KVM. Here the node specs: +1GBits up/down 32GB DDR4 RAM 512GB RAID10 SSD Intel Xeon E5-2680V4 (dedicated for this KVM) Intel Xeon Phi 3120P (shared) If you want I can run a benchmark on my E7 machine. But I doubt it will change a lot.

@PitaJ said in Bookmarks / Favourites breaking change 1.2: How do you recommend this be done? If you want a changelog, you can look at the milestone on GitHub. But milestones only cover issues. There iare of course lot of changes and addition that arent referenced on issues. There were some helpful topics of breaking changes on the past with a little explanation. I guess a topic with centralized information would be nice for 1.2 1.3 1.4 at least updates ( including new or uptades hooks explained + breaking changes on plugins explained + breaking changes on themes explained + a simple explanation of new features) It doesnt need to be all changes just important things Please remember that not every body know to code but with some little explanations and documentation some of us can keep runnin and doing small fixes and learning and improving nodebb

I use nginx as a static file server just as the wiki illustrates. And I added a log to monitor what kind of requests goes to NodeBB server. location ~ ^/(images|sounds|templates|uploads|vendor|src\/modules|nodebb\.min\.js|stylesheet\.css|admin\.css) { root /path/to/nodebb/public/; try_files $uri $uri/ @nodebb; } location / { access_log /var/log/nginx/access3.log; proxy_pass http://io_nodesss; } I found that some of requests of the static files are still going to NodeBB: "GET /src/modules/composer/preview.js?d7bd0222-d024-4aba-869d-0b088e7d5ba1 HTTP/1.1" 200 772 "GET /src/modules/composer/uploads.js?d7bd0222-d024-4aba-869d-0b088e7d5ba1 HTTP/1.1" 200 2539 "GET /src/modules/composer/drafts.js?d7bd0222-d024-4aba-869d-0b088e7d5ba1 HTTP/1.1" 200 492 And I checked that those files are not in ./src/modules, they are at ./node_modules/xxxx/static/ instead. Is there any solution to this? Don't tell me that I should copy those files to /src/modules/ manually.

[image: I8ZyBFL.png] And it looks great!

@esfandiar Yes, take a look at the write API plugin.

I git clone v1.x.x branch. today I git reset --hard fdd8514, then work OK!

In case someone need to do this too, the correct commands are // Remove the list of favorited posts from all users. db.objects.remove({_key: /^uid:\d+:favourites$/}) // Remove the list of users who favourited the post from all posts. db.objects.remove({_key: /^pid:\d+:users_favourited$/}) // Remove the favorite count from all posts. db.objects.updateMany({"_key":/post:[0-9]+/g},{$set: {reputation: 0}})

Thank you, I ran pkg update && pkg upgrade and service nodebb restart and now nodebb is able to install plugins. The redis issue seems to be more a pkg related issue. Searching around, it seems it does happen sometimes, and pwd_mkdb /etc/master.passwd fixes it. Thank you once again, this is a great service.

Interesting thread Whats the tool uses?

hello Devs, is there documentation for nodebb inbuilt libraries (USER,CATEGORIES,POST,META,DB) ?

No need to post a full guide as @yariplus had the correct answer all the time. I just did not understand it at first.

Hey Nodebb team: I am a fan of this custom page plugin. But I dont like default widget in the pages. Is there anyway to write a plugin and override the widget with a few custom HTML and CSS? Thanks, Ethan

Testing testing

It's hard to provide a good answer with no details. What is your NodeBB version and which system do you run it on? Do you use MongoDB or Redis? Do the users on your site get an error, or can't they find anything at all? As admin: Can you change your own profile picture on your own site?