Does the “forever” daemon cache the Node.js script

node.js

Does the "forever" daemon know if I updated my Node.js script?

Is it safe for me to change my Node.js script if the forever daemon is actively running in the background?

Best Answer

Not a definite answer (I have no clue) but merely a hint, have you checked the watch-settings?

From the README on github:

//
// Options for restarting on watched files.
//
'watch': false              // Value indicating if we should watch files.
'watchIgnoreDotFiles': null // Dot files we should read to ignore ('.foreverignore', etc).
'watchIgnorePatterns': null // Ignore patterns to use when watching files.
'watchDirectory': null      // Top-level directory to watch from.

Edit: So, guessing from these options, it probably does "cache" the script, in the sense that it reads its source once - unless you tell it to watch the source.

Related Solutions

Ubuntu – cant get upstart script for node.js program to start on startup

The startup event is the very first event that gets emitted in the Upstart bootup process. There are all kinds of things that won't have happened yet - the root filesystem will still be mounted read-only, networking hasn't been initialized, etc.

I suspect that the job is exiting quickly because all of its dependencies (explicit or implicit) aren't initialized yet. I'd change the start condition to something like

start on filesystem and started networking

At least then you'll be able to write to your logfile.

As a side note, it looks like you reversed your output redirection arguments - you actually meant >> /var/log/node.log 2>&1. Using 2>&1 means "take whatever is currently fd 1, and make fd 2 the same thing", but you haven't changed what stdout is yet.

Does it make sense to reverse proxy Node.js through Apache

I would suggest that setting up Apache to reverse proxy to Node.js is against the intent of Node.js. Node is very lightweight - its overhead is minimal. Launching an apache process to handle the Node.js stream negates the point of using Node.js (essentially, you would be limited by the performance of Apache).

Node is sometimes not considered stable enough to run without monitoring and might not be the ideal front end. I might suggest placing either Squid or HAproxy in front of Node and Apache, allow either of those to serve as your proxy, and run Node and Apache on different ports (e.g. 8080, 8081). Both Squid and HAProxy have good performance and should meet your needs without detracting from either backend server.

Best Answer

Related Solutions

Ubuntu – cant get upstart script for node.js program to start on startup

Does it make sense to reverse proxy Node.js through Apache

Related Topic