CODEWITHSUNDEEP
node.jsforemanforever
joshy
joshy

Reputation: 70

Node packages seems to be doing nothing

I'm running a little Socket.io & Express app on an Ubuntu server and I'm trying to use forever module.

However it seems that it doesn't matter which package I install nothing seems to be happening. I've run 

sudo npm install  forever -g

On install I am getting this message:

npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.25","npm":"1.3.10"}

However typing the function forever start app.js just returns to the next line.

$:/home/app$ forever start app.js
$:/home/app$

Typing which forever returns 

/usr/local/bin/forever

I seem to be getting similar issues for nodemon and foreman, I have no idea why. Any ideas what I'm missing?

Upvotes: 0

Views: 820

Answers (2)

DonRichards
DonRichards

Reputation: 146

Not to sound like a hater but I stopped using forever because they stopped developing it. It has a few issues specifically if you launch an app with it in the startup process you can't see the process to terminate or restart.

Try nodemon, it works best for me and has most of the same options. I know this isn't the answer you were looking for but I hope you'll avoid the same issues I ran into. Good luck

Upvotes: 0

ffflabs
ffflabs

Reputation: 17511

The warning you get happens because of hard dependencies on node 0.8, but it's customary to just ignore them. Just to try, I installed forever on a fresh Ubuntu 14.04 and got a lot of warnings

npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})
npm WARN engine [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"v0.10.29","npm":"1.4.14"})

but after that, if I call the forever help screen

forever -h

it displays normally.

Are you executing forever in the same path that your app.js is? What happens if you call forever list after running forever start? What user are you running forever as? Are you sure that running node app.js runs normally?

Upvotes: 0

Related Questions