The idea that Redis stores everything in-memory is the key to its speed. However, it's also a huge crutch in that yes... the less-often used data is still in-memory when it could rightly just be put in the hard drive and queued up when needed. That's why we suggested migrating to Mongo, because, well... it does just that

@teh_g sadly, this won't be possible with Electron, since it requires V8, Chromium and Node.JS to run, all of which are not available on neither iOS nor Android. You could maybe use Cordova for this, but it would require a C# developer, store licenses etc... not forget a great amount of time and effort. Electron, on the other hand, makes developing Desktop applications with JS easy and really quick... So it would be quite easy to craft a NodeBB client. I imagine board admins could run an installer like npm install nodebb-electron-client-setup, then do npm setup and have the client available for download at http://example.tld/client/:os for their users.

@Moritz-Friedrich solved it somehow ugly by starting the tests in a "ready" callback. Is there some way to find out whether downloaded code has been fully executed?

@julian [image: f0197563dda2a48d34396a5881b6729a.jpg] I like NodeBB's source, though it would be nice to have real documentation for it Maybe even something like consistent JSDoc comments? Thank you for the kind words, by the way. I'll keep updating this post from time to time

I noticed that whenever I reload nodebb, I get error messages like this one in the log: 31/7 23:47 [12036] - error: Error: Failed to lookup view "500" in views directory "/var/www/node/nodebb/public/templates" at EventEmitter.render (/var/www/node/nodebb/node_modules/express/lib/application.js:579:17) at ServerResponse.render (/var/www/node/nodebb/node_modules/express/lib/response.js:961:7) at ServerResponse.res.render (/var/www/node/nodebb/src/middleware/middleware.js:337:10) at /var/www/node/nodebb/src/routes/index.js:223:9 at /var/www/node/nodebb/src/middleware/middleware.js:192:12 at /var/www/node/nodebb/node_modules/async/lib/async.js:589:17 at done (/var/www/node/nodebb/node_modules/async/lib/async.js:126:15) at /var/www/node/nodebb/node_modules/async/lib/async.js:32:16 at /var/www/node/nodebb/node_modules/async/lib/async.js:586:21 at /var/www/node/nodebb/node_modules/templates.js/lib/templates.js:160:12 Error: Failed to lookup view "500" in views directory "/var/www/node/nodebb/public/templates" at EventEmitter.render (/var/www/node/nodebb/node_modules/express/lib/application.js:579:17) at ServerResponse.render (/var/www/node/nodebb/node_modules/express/lib/response.js:961:7) at ServerResponse.res.render (/var/www/node/nodebb/src/middleware/middleware.js:337:10) at /var/www/node/nodebb/src/routes/index.js:223:9 at /var/www/node/nodebb/src/middleware/middleware.js:192:12 at /var/www/node/nodebb/node_modules/async/lib/async.js:589:17 at done (/var/www/node/nodebb/node_modules/async/lib/async.js:126:15) at /var/www/node/nodebb/node_modules/async/lib/async.js:32:16 at /var/www/node/nodebb/node_modules/async/lib/async.js:586:21 at /var/www/node/nodebb/node_modules/templates.js/lib/templates.js:160:12 I think it is users trying to access the page while reloading, but it made me wonder if there is a way to prevent this from happening? Also, I have currently three worker threads enabled. Shouldn't they be restarted successively so every request can be handled?

@julian, here it is. Thank you for your time!

@baris said: When you follow another user, you get a notification when they post a new topic. Following them also adds them to the contacts list on the /chats page. Yep, you are right, my bad. Didn't have these in mind...

Inside of the client script... Anyway, I just restarted NodeBB and tried it again, it works fine now Thank you!

@baris you have any solution for the Cat A.1.1 ?

Nope- problem seems gone now, since the machine migration everything is fine and I get no more errors. Thanks though

Noooo, they would have been so cool!

@Moritz-Friedrich said: Weird enough, I just realized that at the old subdomain (as a CNAME) logging in is still possible... Default this is not set to anything, so this doesn't need to be set... afaik

@julian said: So I'd have to make multiple hits against the database to check if the following users exist: John John Frikkin John Frikkin Doe John Frikkin Doe how John Frikkin Doe how are John Frikkin Doe how are you John Frikkin Doe how are you today See the problem? I thought about this while posting the thread. I think I'll just disallow spaces in usernames But hey, thank you for the extensive reply!

@a_5mith , yes, that is what I meant - those comments would be pretty ugly in production code, but to debug your own templates it would be nice to see where something comes from straight out of the browser. Especially when you - like me - just started working with NodeBB.