How to allow restarting when using Forever?

Nicekiwi

I run my NodeBB system setup using:

forever start app.js.

But I've just realised than running the app like this prevents me from restarting it inside the admin (Clicking the restart button does nothing), how can I fix this?

When running via ./nodebb start, it works fine of course. But that drops Forever.

julian

@Nicekiwi Any reason you want to use forever? If NodeBB crashes, it will bring itself back up, negating the advantage of forever.

If you still want to use forever, try forever start loader.js

Nicekiwi

@julian it does!?

Since when?

Are those docs about keeping it running only for Dev purposes?

404 Not Found

(docs.nodebb.org)

"However, bear in mind that crashes will cause the NodeBB process to halt, bringing down your forum. Consider some of the more reliable options, below:"

Leading to Forever.

a_5mith

@Nicekiwi it will attempt to restart 3 times before halting the process, so if you've got a plugin error, in the logs you'll get experienced 3 Halts, stopping, no amount of forever or supervisor would help you in that scenario.

julian

Oh boy, you know... Perhaps it's time I updated that article!

Nicekiwi

@julian yeah...

@a_5mith, heaps of the plugins seem to have errors though and theres no way to tell if a plugin is stable before you install it. Is there?

a_5mith

Not yet, should be coming soon though with the changes to the ACP plugins list.

Nicekiwi

Excellent

a_5mith

@Nicekiwi You can go to the github repo of the plugin and see when it was last updated, recent ones are guaranteed to work (unless they're mine and I've not finished them yet.)

Anything updated in the last 2 months or so will work, as 0.4.0 or 0.4.3 brought in a few changes to the plugin system.

So if any of the commits have "support for 0.4.x" in them, they're probably fine.

julian

A number of changes to v0.5.0 end up breaking a whole bunch of plugins. But the good news is after v0.5.0, we'll enter a non-breaking-change phase where successive patch versions (v0.5.1, 0.5.2, etc) will not break compatibility... or we'll try not to, rather.