@PitaJ Hey I did everything it was working I fixed the issue that was above I forgot what I did but I wanted to put is at my ip so when I get the domain name I can just redirect and such now it does this whenever I try changing the config for the url 025c0b31-ff60-44ae-a2cf-291ac76d0e60-image.png
Is there a note somewhere on compatibility with NodeJS releases?
I am installing NodeBB for a client. I installed a staging version a month or two back. I'm aware that Node now has two new branches - 4.x LTS and 5.
I want to install a version of NodeBB locally so that I can test some plugins. Whats the best version of NodeJS to go with as at November 2015 both for local testing and production use? I
The staging version I installed was NodeBB 0.8
OS is CentOS release 6.7 (Final)
NodeJS is currently v0.10.36. NPM is 2.14.1
Any hints on the most painless way to upgrade NodeJS if that is appropriate also gratefully received Would rather avoid hours of dependency hell.
Most painless way to upgrade node is via chris-lea ppa: https://launchpad.net/~chris-lea/+archive/ubuntu/node.js-devel
NodeBB is cleared to work on Node v4 on v0.9.0 only, which has not been released yet (
v0.8.x, you are cleared to use up to v0.12 of Node.js.
@julian thanks but this is a CentoOS box so don't think the ppa applies.
Do you know if 0.9 works with Node 4.2.1 & 5? The reason I ask is that a vagrant box I am using comes with 5.0 pre-installed so that's no good if I need earlier versions.
@codecowboy out probably works with those. I would suggest using NVM for Node installation and everything. The roll install via curl sh script.
@pitaj not sure what you mean by 'out' or 'roll'
I was able to use nvm to use node 0.12 and everything is working. Thanks all.
@codecowboy those were typos caused by autocorrect on mobile which I didn't catch.
Should be "it" and "whole" I think