running a NodeJS process with forever-monitor on development server
up vote
0
down vote
favorite
I am attempting to run my expressJS app continuously
on a server using forever-monitor.
I don't get any errors however my app does not keep running as expected,
the process exits after 3 restarts.
Can I omit the max value here or what am I missing to run the app continuously?
Info: I am deploying it to a AWS lightsail server.
the code I have implemented comes from the forever-monitor git repo.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max: 3,
silent: true,
args:
});
child.on('exit', function () {
console.log('program has exited after 3 restarts');
});
child.start();
node.js amazon-lightsail forever-monitor
add a comment |
up vote
0
down vote
favorite
I am attempting to run my expressJS app continuously
on a server using forever-monitor.
I don't get any errors however my app does not keep running as expected,
the process exits after 3 restarts.
Can I omit the max value here or what am I missing to run the app continuously?
Info: I am deploying it to a AWS lightsail server.
the code I have implemented comes from the forever-monitor git repo.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max: 3,
silent: true,
args:
});
child.on('exit', function () {
console.log('program has exited after 3 restarts');
});
child.start();
node.js amazon-lightsail forever-monitor
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am attempting to run my expressJS app continuously
on a server using forever-monitor.
I don't get any errors however my app does not keep running as expected,
the process exits after 3 restarts.
Can I omit the max value here or what am I missing to run the app continuously?
Info: I am deploying it to a AWS lightsail server.
the code I have implemented comes from the forever-monitor git repo.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max: 3,
silent: true,
args:
});
child.on('exit', function () {
console.log('program has exited after 3 restarts');
});
child.start();
node.js amazon-lightsail forever-monitor
I am attempting to run my expressJS app continuously
on a server using forever-monitor.
I don't get any errors however my app does not keep running as expected,
the process exits after 3 restarts.
Can I omit the max value here or what am I missing to run the app continuously?
Info: I am deploying it to a AWS lightsail server.
the code I have implemented comes from the forever-monitor git repo.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max: 3,
silent: true,
args:
});
child.on('exit', function () {
console.log('program has exited after 3 restarts');
});
child.start();
node.js amazon-lightsail forever-monitor
node.js amazon-lightsail forever-monitor
asked Nov 9 at 11:05
timber535
106
106
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29
add a comment |
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I had to install both forever and forever-monitor dependencies to get the app running continuously.
The application runs as expected now after closing the CLI session.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max:3,
silent: true,
sourceDir: '/app.js',
watch:true,
args:
});
child.on('watch:restart', function(info) {
console.error('Restaring script because ' + info.file + ' changed');
});
child.on('restart', function() {
console.error('Forever restarting script for ' + child.times + ' time');
});
child.on('exit:code', function(code) {
console.error('Forever detected script exited with code ' + code);
});
child.start();
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I had to install both forever and forever-monitor dependencies to get the app running continuously.
The application runs as expected now after closing the CLI session.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max:3,
silent: true,
sourceDir: '/app.js',
watch:true,
args:
});
child.on('watch:restart', function(info) {
console.error('Restaring script because ' + info.file + ' changed');
});
child.on('restart', function() {
console.error('Forever restarting script for ' + child.times + ' time');
});
child.on('exit:code', function(code) {
console.error('Forever detected script exited with code ' + code);
});
child.start();
add a comment |
up vote
0
down vote
accepted
I had to install both forever and forever-monitor dependencies to get the app running continuously.
The application runs as expected now after closing the CLI session.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max:3,
silent: true,
sourceDir: '/app.js',
watch:true,
args:
});
child.on('watch:restart', function(info) {
console.error('Restaring script because ' + info.file + ' changed');
});
child.on('restart', function() {
console.error('Forever restarting script for ' + child.times + ' time');
});
child.on('exit:code', function(code) {
console.error('Forever detected script exited with code ' + code);
});
child.start();
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I had to install both forever and forever-monitor dependencies to get the app running continuously.
The application runs as expected now after closing the CLI session.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max:3,
silent: true,
sourceDir: '/app.js',
watch:true,
args:
});
child.on('watch:restart', function(info) {
console.error('Restaring script because ' + info.file + ' changed');
});
child.on('restart', function() {
console.error('Forever restarting script for ' + child.times + ' time');
});
child.on('exit:code', function(code) {
console.error('Forever detected script exited with code ' + code);
});
child.start();
I had to install both forever and forever-monitor dependencies to get the app running continuously.
The application runs as expected now after closing the CLI session.
var forever = require('forever-monitor');
var child = new (forever.Monitor)('app.js', {
max:3,
silent: true,
sourceDir: '/app.js',
watch:true,
args:
});
child.on('watch:restart', function(info) {
console.error('Restaring script because ' + info.file + ' changed');
});
child.on('restart', function() {
console.error('Forever restarting script for ' + child.times + ' time');
});
child.on('exit:code', function(code) {
console.error('Forever detected script exited with code ' + code);
});
child.start();
edited Nov 12 at 11:36
answered Nov 9 at 13:59
timber535
106
106
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53224535%2frunning-a-nodejs-process-with-forever-monitor-on-development-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The documentation on GitHub says that 'max' is an option. So you should be able to just omit it.
– K Mo
Nov 9 at 11:17
Thanks for your quick reply, would it be better to set it to another value?
– timber535
Nov 9 at 12:29