forever

问题 This question already has answers here : Restart node upon changing a file (8 answers) Closed 4 years ago . I found that forever can run nodejs server forever. Is forever supports this feautre? -- If the nodejs script is modified changed, the server shld restarted automatically. How can I enable this feature using forever? or I need something else? 回答1: I personally use Nodemon to handle that. Its a replacement for the node server. It automatically restarts the server when your files are

问题 On a free-tier Amazon EC2 instance, I set up a simple node.js Hello World app running on express. If I run npm start , my app runs fine and I can hit it from my browser, and I see the following output: > myappname@0.0.0 start /home/ec2-user/app > node ./bin/www I have installed the forever tool globally. When I run forever start app.js , I see: warn: --minUptime not set. Defaulting to: 1000ms warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms info:

问题 I am trying to run MongoDB server forever locally on Windows 10. And for that I'm using forever server.js which throws an error i.e, Forever is not installed. I did npm install. But then too showing the same error. I have followed this guide, but it's for Ubuntu. I am using Windows 10. I need something like if I close the server cmd also, it should keep running. 回答1: In Windows, you can use the mongod command to register Mongo as a service mongod --directoryperdb --dbpath "C:\Program Files

问题 I used to start my application using: DEBUG=chakka ENVIRONMENT=production npm start How can i start it using forever so i wouldn't have to do it everytime i want to test the application? Thanks! 回答1: First you need to know what the application's main script file is. Open up your package.json file and find out what the start script is. If you're using Express it might be app.js . So we'll assume app.js for this example, replace with whatever your file is. To start the application: DEBUG=chakka

问题 I'm trying to deploy a node js server on a remote machine by a post-commit hook, which would call a script on the remote machine that does the actual deployment. The problem I'm facing is if I run the remote script on the machine it works fine, but when I try to execute the same script by an ssh command the server doesn't start. This is what my post commit hook looks like: #!/bin/bash #Connect to AWS machine and run deploy script ssh -i ~/Documents/aa-kp-inst1.pem ubuntu@<remote-ip> "sh /home

问题 I have a simple bash script written that auto-deploys code to my Node.js server whenever a commit is made, then restarts the server using forever. This script is run periodically on a cronjob. Oh yeah, the site is still in the dev phase before being released, hence the constant server restarting. :) The script does some other things, but the real interesting part is the following two lines of code: forever stopall forever start app.js When I run the script manually from the command-line

问题 I'm trying to setup forever and NodeJS to monitor&restart my app and also keep it running when exits. Currently I have this: var forever = require("forever-monitor"); var child = new(forever.Monitor)('main.js', { 'silent': false, 'pidFile': '../pids/app.pid', 'sourceDir': '.', 'watch': true, 'watchDirectory': '.', 'watchIgnoreDotFiles': null, 'watchIgnorePatterns': null, 'logFile': '../logs/forever.log', 'outFile': '../logs/forever.out', 'errFile': '../logs/forever.err' }); child.start();

问题 I am having hard time understanding what is forever in nodejs. Can someone explain what is forever in simplest way that i can understand and what is the purpose of it 回答1: forever is a node.js package that is used to keep the server alive even when the server crash/stops. When the node server is stopped because of some error, exception, etc. forever automatically restarts it From the npmjs https://www.npmjs.com/package/forever A simple CLI tool for ensuring that a given node script runs

问题 I am looking to daemonize my Node.js application. What's the difference between upstart and forever? Also, are there other packages I might want to considering looking at? 回答1: As pointed out in the comments, upstart will be used to start the forever script, since upstart has hooks for system events (like shutdown and startup of your server). The other differences are: Upstart was developed for Linux, while forever is platform-independent. Forever is specific to nodejs, and has some pretty

问题 I have installed nodejs using: apt-get install nodejs Then i have installed npm using: apt-get install npm And then i have installed forever using: npm install forever -g Now i go to my project /var/www/myproject and attempt to run forever start server.js then i get the following message: /usr/bin/env: node: No such file or directory Can anyone tell me whats going on? 回答1: EDIT: As of December 2018, this is no longer the correct way. See the other two answers. You need to symlink the nodejs