voted. nodeBB is the next generation of forum SW.

• No PHP
• scalable NoSQL backend
• JavaScript

This is a no brainer!

@frissdiegurke Knowing what I know now, @julian post can be construed to contain all the information :). I would word it differently though as SSO is probably veyr widely used. And if so, then calling port optional is...well, still technically correct.

If you move your mouse over bottom right there appear a funky button. A very obscure feature indeed.

What pages specifically do you refer to?

If you have the numbers just post them.

Guys, could you take a look at pull requests pls?

https://github.com/NodeBB/NodeBB/pull/2926

Btw, I did sign CLA before. Though CLAhub lately just errors out

@frissdiegurke Knowing what I know now, @julian post can be construed to contain all the information :). I would word it differently though as SSO is probably veyr widely used. And if so, then calling port optional is...well, still technically correct.

Finally upgraded to 0.6.1 from 0.5.7. First I added the port (in my case 8080) to the URL string as described in this thread. That screwed up SSO. Both google and facebook. After, I went back and manually added "port" setting into config.json, SSO seems functional. This appears to be a bug or a logical conflict. Basically SSO is not functional unless your URL string is exactly how you access nodeBB from the outside.

That brings up a feature request. I would like to have an unlisted category. A perfectly ordinary category, just not listed on the home page. Something where I want to list some basic reference information, which is not important enough to keep on the Home page. Is there a way to achieve that?

@xtech If you have an example where mobile scrolling is implemented well within a browser, please post a link

@agarcia17 I looked at templates.js library. I do not think it supports that now.

https://github.com/psychobunny/templates.js/blob/master/lib/templates.js

I got it, now that I understand what installs redis.

The way I upgrade is I create a brand new workspace, install a new version of nodebb, copy over the config.json. I think that makes sense in real deployment scenario versus executing "git pull" in place. This way I retain a fully functional prior version installation I can fall back to in a instant should something fail with a new version.

@dwn Maybe that is the problem. I copied config.json from another workspace instead of running ./nodebb setup