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();









share|improve this question






















  • 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

















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();









share|improve this question






















  • 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















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();









share|improve this question













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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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




















  • 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














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();





share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    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

























    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();





    share|improve this answer



























      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();





      share|improve this answer

























        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();





        share|improve this answer














        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();






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 12 at 11:36

























        answered Nov 9 at 13:59









        timber535

        106




        106






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            這個網誌中的熱門文章

            Xamarin.form Move up view when keyboard appear

            Post-Redirect-Get with Spring WebFlux and Thymeleaf

            Anylogic : not able to use stopDelay()