running npm application using forever start in server












0















I have an angular 6 application with typescript and webpack.



This angular application has backend for serving api calls and the backend is running as a separate application.



To start the application in my local, From the project home folder,




npm start




To build the application,




npm run build




When I run the above command, I get, dist folder which has the follwoings.



- index.html
- assets
- fonts
- icon
- img
- main.sdgsdgfdsff.css
- main.sdfgsdfgdsfg.js
- manifest.3asdasdfsad.bundle.js
- polyfills.3462436425654af34.bundle.js
- vendor.sdgsdfg3453244354.bundle.js
- webpack-assets.json
- server
- config.js
- index.js
- routes.js
- socket.js


Now, I would like to run this application in a remote server.



So, copied the entire dist folder and tried the following.




forever start -o otput.log server/index.js




The console logs,



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: Forever processing file: server/index.js


In output.log.



Node NOT Exiting...


Nothing is happening.



My goal is to start this in a remote server. Not sure what am i missing here.



I tried forever in my local mac also.




forever start -o otput.log server/index.js




I installed the below stuffs also.




npm install express compression forever minimum-tls-version body-parser fs https path
method-override











share|improve this question

























  • use nodemon or nginx to serve the application on remote server

    – swanand keskar
    Nov 17 '18 at 5:51











  • Nodemon is for development. I am looking for running in production.

    – user1578872
    Nov 17 '18 at 5:53











  • nginx is suitable for production

    – swanand keskar
    Nov 17 '18 at 5:57











  • Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

    – xan_z
    Nov 17 '18 at 6:31
















0















I have an angular 6 application with typescript and webpack.



This angular application has backend for serving api calls and the backend is running as a separate application.



To start the application in my local, From the project home folder,




npm start




To build the application,




npm run build




When I run the above command, I get, dist folder which has the follwoings.



- index.html
- assets
- fonts
- icon
- img
- main.sdgsdgfdsff.css
- main.sdfgsdfgdsfg.js
- manifest.3asdasdfsad.bundle.js
- polyfills.3462436425654af34.bundle.js
- vendor.sdgsdfg3453244354.bundle.js
- webpack-assets.json
- server
- config.js
- index.js
- routes.js
- socket.js


Now, I would like to run this application in a remote server.



So, copied the entire dist folder and tried the following.




forever start -o otput.log server/index.js




The console logs,



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: Forever processing file: server/index.js


In output.log.



Node NOT Exiting...


Nothing is happening.



My goal is to start this in a remote server. Not sure what am i missing here.



I tried forever in my local mac also.




forever start -o otput.log server/index.js




I installed the below stuffs also.




npm install express compression forever minimum-tls-version body-parser fs https path
method-override











share|improve this question

























  • use nodemon or nginx to serve the application on remote server

    – swanand keskar
    Nov 17 '18 at 5:51











  • Nodemon is for development. I am looking for running in production.

    – user1578872
    Nov 17 '18 at 5:53











  • nginx is suitable for production

    – swanand keskar
    Nov 17 '18 at 5:57











  • Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

    – xan_z
    Nov 17 '18 at 6:31














0












0








0








I have an angular 6 application with typescript and webpack.



This angular application has backend for serving api calls and the backend is running as a separate application.



To start the application in my local, From the project home folder,




npm start




To build the application,




npm run build




When I run the above command, I get, dist folder which has the follwoings.



- index.html
- assets
- fonts
- icon
- img
- main.sdgsdgfdsff.css
- main.sdfgsdfgdsfg.js
- manifest.3asdasdfsad.bundle.js
- polyfills.3462436425654af34.bundle.js
- vendor.sdgsdfg3453244354.bundle.js
- webpack-assets.json
- server
- config.js
- index.js
- routes.js
- socket.js


Now, I would like to run this application in a remote server.



So, copied the entire dist folder and tried the following.




forever start -o otput.log server/index.js




The console logs,



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: Forever processing file: server/index.js


In output.log.



Node NOT Exiting...


Nothing is happening.



My goal is to start this in a remote server. Not sure what am i missing here.



I tried forever in my local mac also.




forever start -o otput.log server/index.js




I installed the below stuffs also.




npm install express compression forever minimum-tls-version body-parser fs https path
method-override











share|improve this question
















I have an angular 6 application with typescript and webpack.



This angular application has backend for serving api calls and the backend is running as a separate application.



To start the application in my local, From the project home folder,




npm start




To build the application,




npm run build




When I run the above command, I get, dist folder which has the follwoings.



- index.html
- assets
- fonts
- icon
- img
- main.sdgsdgfdsff.css
- main.sdfgsdfgdsfg.js
- manifest.3asdasdfsad.bundle.js
- polyfills.3462436425654af34.bundle.js
- vendor.sdgsdfg3453244354.bundle.js
- webpack-assets.json
- server
- config.js
- index.js
- routes.js
- socket.js


Now, I would like to run this application in a remote server.



So, copied the entire dist folder and tried the following.




forever start -o otput.log server/index.js




The console logs,



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: Forever processing file: server/index.js


In output.log.



Node NOT Exiting...


Nothing is happening.



My goal is to start this in a remote server. Not sure what am i missing here.



I tried forever in my local mac also.




forever start -o otput.log server/index.js




I installed the below stuffs also.




npm install express compression forever minimum-tls-version body-parser fs https path
method-override








node.js angular npm forever






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 5:39







user1578872

















asked Nov 17 '18 at 5:20









user1578872user1578872

1,60452565




1,60452565













  • use nodemon or nginx to serve the application on remote server

    – swanand keskar
    Nov 17 '18 at 5:51











  • Nodemon is for development. I am looking for running in production.

    – user1578872
    Nov 17 '18 at 5:53











  • nginx is suitable for production

    – swanand keskar
    Nov 17 '18 at 5:57











  • Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

    – xan_z
    Nov 17 '18 at 6:31



















  • use nodemon or nginx to serve the application on remote server

    – swanand keskar
    Nov 17 '18 at 5:51











  • Nodemon is for development. I am looking for running in production.

    – user1578872
    Nov 17 '18 at 5:53











  • nginx is suitable for production

    – swanand keskar
    Nov 17 '18 at 5:57











  • Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

    – xan_z
    Nov 17 '18 at 6:31

















use nodemon or nginx to serve the application on remote server

– swanand keskar
Nov 17 '18 at 5:51





use nodemon or nginx to serve the application on remote server

– swanand keskar
Nov 17 '18 at 5:51













Nodemon is for development. I am looking for running in production.

– user1578872
Nov 17 '18 at 5:53





Nodemon is for development. I am looking for running in production.

– user1578872
Nov 17 '18 at 5:53













nginx is suitable for production

– swanand keskar
Nov 17 '18 at 5:57





nginx is suitable for production

– swanand keskar
Nov 17 '18 at 5:57













Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

– xan_z
Nov 17 '18 at 6:31





Try to use forever in verbose mode - add --verbose in the command - or simply run node server/index.js and see what you get . Also have you placed the dist folder in the correct relative location ?

– xan_z
Nov 17 '18 at 6:31












0






active

oldest

votes











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',
autoActivateHeartbeat: false,
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%2f53348482%2frunning-npm-application-using-forever-start-in-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53348482%2frunning-npm-application-using-forever-start-in-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







Popular posts from this blog

Guess what letter conforming each word

Port of Spain

Run scheduled task as local user group (not BUILTIN)