I added support for 2 important nodejs directives. The directives can be passed as follows:
forever --noUseIdleNotification --exposeGC
if the directives are explicitly specified, they are passed to the argument-list when spawning the node process. Currently there's no other way to pass these directives since they need to be placed before the js file name when spawning nodejs.
here's a reference to a discussion about this issue in stackoverflow
The change is also reflected in the forever-monitor's monitor.js file.
Added support for nodejs '--nouse-idle-notification' and '--expose-gc…
We need a more generic solution, allowing us to pass any arguments to node. I'll update when I think about how to resolve this.
updated forever to support any arguments passed to the command e.g.
-c "node --nouse-idle-notification --expose-gc"
Have a look at the changes I've made. It now supports any arguments that are passed together with the command. For example: forever -c "node --nouse-idle-notification --expose-gc"
I'd be happy to hear your thoughts. As you probably know the "--nouse-idle-notification" has some significant implications on node's performance. I cannot use forever in production unless I can pass this directive.
What happened with this?, I'm needing to send that parameters.
No reply here. Use my branch. It works for me.
Will do, thanks!
This is fixed with foreverjs/forever-monitor#8
This is fixed in forever-monitor, until we publish a new version to npm this will maintain open
+1 we definitely need support for this. is there an eta on the next npm version?
[fix dist] Update to the latest `forever-monitor`. Fixes #361.
Fixed. The --command option will now get passed to the latest version of forever-monitor so it will parse it correctly.