I run my game forum on the current master, well, just because there is not a lot there and it can be broke if I have to.
I updated git just now and ran ./nodebb upgrade and received the following. Everything is currently working, just wanted to report the warning.
[root@daermabb nodebb]# ./nodebb upgrade
1. Bringing base dependencies up to date...
Error: Command failed: /usr/bin/env npm i --production
npm ERR! Linux 3.10.0-229.20.1.el7.x86_64
npm ERR! argv "/root/.nvm/v0.12.9/bin/node" "/root/.nvm/v0.12.9/bin/npm" "i" "--production"
npm ERR! node v0.12.9
npm ERR! npm v2.14.9
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package email@example.com does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer firstname.lastname@example.org wants redisearch@^0.0.6
npm ERR! Please include the following file with any support request:
npm ERR! /opt/daerma/nodebb/npm-debug.log
[root@daermabb nodebb]# ./nodebb start
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB
[root@daermabb nodebb]# ./nodebb log
Type Ctrl-C to exit
Clustering enabled: Spinning up 1 process(es).
7/12 09:16  - info: Time: Mon Dec 07 2015 09:16:57 GMT-0600 (CST)
7/12 09:16  - info: Initializing NodeBB v0.9.1
7/12 09:16  - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
info: Imgbed: regex recalculated: (?<paren>[\(]\s*)?(?<url>https?://[^\s]+\.(jpg|jpeg|gif|gifv|png|svg))
7/12 09:17  - info: NodeBB Ready
7/12 09:17  - info: Enabling 'trust proxy'
7/12 09:17  - info: NodeBB is now listening on: 0.0.0.0:4567
I was having some issues with NPM a few days ago which was timing out, but was a issue with ports due to my firewall setup. So check to make sure git port is not being blocked.
Also could be an issue with the way your cloning. Was having issues cloning from another git like gitlab vs github, turns out the git:// git:link was the issue try adding that to the front if using SSH cloning.