Technical Support

I would like users to have different dashboards (content) depending on the "groups" the user has subscribed to. Also how would one go about storing additional user info in Mongo?

@countach that's nothing to be worried about for now. It's something that needs to be taken care of on the theme's end. Post an issue on the theme's repository.

@pitaj

Got it figured out. Basically, you have to form a "redirect chain" kinda. I think I was creating an infinite loop of redirection or excluding a specific case (www. for 443 and for 80 separately) in my above nginx config. I ended up having to redirect 80 http://www.domain.com, 80 http://domain.com AND 443 https://www.domain.com all to 443 https://domain.com and then that third block is where all the master logic for the activity goes, if that makes sense.

In my original post, I was combining too many of these cases into just 2 blocks. In addition, I also added location / {} and wrapped that around my return 301 statements.

This fixed the problem entirely with both the domain and the forum malfunctioning. Last but not least, I wanted to mention that I also added proxy_set_header X-Forwarded-Proto $scheme; to the main logic block near the other proxy_set settings, which fixed a csrf error as well. So we're all good now!

Very exciting stuff. I appreciate the quick replies and help. Happy to use NodeBB for my new site!

@baris Okay: I'll focus on the possibility of multiple nodebb processes.

@PitaJ: Gotcha. I'm glad I put exactly what I typed so that you could point out my error. I revisited the documentation and it looks like I'm not starting the app the way it's currently recommended (via nodebb start), so, without having insight into why running node app.js might be a problem, I'm giving that a shot.

With that, the nodebb related output seems to be the same when grepping either 'node' or 'nodebb'... it shows processes for loader.js and app.js in the nodebb directory.

Anyway--I'll see what happens with today's digest. Regardless, I appreciate everyone's help very much.

@Eric-Ladner No, it doesn't upgrade the plugins... or I should say, it didn't used to.

More recent versions of NodeBB call ./nodebb upgradePlugins as part of the upgrade process, and that will upgrade plugins (to whatever version nbbpm says they should be upgraded to)...

However, those plugins that aren't registered with nbbpm won't be touched by ./nodebb upgradePlugins.

It is a custom install, we are trying to get it updated to the latest in steps to ensure nothing is broken.

nodebb mobules should either start with nodebb-plugin- or nodebb-theme- so in your case your theme name should be nodebb-theme-exo-theme

@pitaj Yes true, I tried installing mongo onto my 17.04. The installation was successful but some packages did not work (were not supported).

I had the same problem when I was playing with NodeBB on a $2.5 vps from Vultr (=512MB ram). htop shows me that build process uses all available ram and cpu. Deploying on a decent machine/vps would solve the problem, aternatively, I called build steps one at a time ( eg ./nodebb build languages , ./nodebb build 'client side styles' etc) . Hope this helps.

we will writing a detail install nodebb with redis or mongodb？

@ljhardy said in Upgrading to Nodebb v1.5.1:

I'm using mongodb, why would sqllite be referenced?

Um, you tell me 😄 That was the output in your installer script!

output of npm i

node scripts/install.js

npm WARN prefer global [email protected] should be installed with -g

[email protected] postinstall /home/ljhardy/public_html/nodebb/nodebb/node_modules/jsonpath
node lib/aesprim.js > generated/aesprim-browser.js

[email protected] install /home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3
node-pre-gyp install --fallback-to-build

[sqlite3] Success: "/home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3/lib/binding/node-v46-linux-x64/node_sqlite3.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

@Adam-Poniatowski & @HARIOM-VASHISTH:

I've managed to migrate my NodeBB to Google Cloud and it's running in clustered mode.

However, I'm having issues with traffic spikes which clog my CPU.

Any of you have experience running multiple instances and autoscaling? (or perhaps @julian can give some input here)

Thanks!!!

Sharing is caring 😛 Better to set code free ...

@jarko You can check out the latest master branch to get those changes. It's still technically v1.5.1.

@sharonyue You would need to modify the files inside your theme folder, e.g. /node_modules/nodebb-theme-persona/. Keep in mind, these files are overwritten when you update.

ok, after reactivated my plugins one by one, I found it was "nodebb-plugin-html5videoplayer"

I know this is rather old but just wanted to share that we suffered a similar issue on our dev forum this morning.
Turns out it was due to our redis cache running out of memory and crashing.

@julian 0_1498737455930_1ad93055-b0f0-4a3f-a362-00629d4ac3a2-image.png

I have also upgrade my nodebb in case this will help solve it,

nodebb upgrade completed, but dashboard still showing a 1.4.4 version and asking me to upgrade?