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.

@Baerrus Where you at with SEO so far?

Looks like its only in 0.6.x

@Baerrus It shouldn't, because following a topic will notify you of a new post in that topic, but that topic won't appear in Unread. They're two different features. Unless there's a specific check in NodeBB that I'm not aware of. Wouldn't be too difficult for me to test if you need a definitive answer.

@baris said: A few weeks ago we weren't checking the slug for correctness. So https://community.nodebb.org/topic/2647/anythinghere was working. But if you had images in the topic in the form of  this was causing an api call to the topic and loading the entire topic to solve that we started checking the slug. If we can find a solution to that image problem we can go back to ignoring the slug. Ah right, that makes sense.

Just checked the code seems like only registered users are counted for views, will fix that. Fixed in https://github.com/NodeBB/NodeBB/commit/55a5d56989c2cdb15e422f0a0047cf7f9b25f31b

@Baerrus said: The is a key moderator functionality to relocate content that users post into a wrong category Thread Tools > Move Topic