javascript - Node Forever Affects App Display (Style and Routes) -

-

i trying make app server run indefinitely forever , nodemon. so, using following command: 

forever -c nodemon --exitcrash app.js

the problem presence of forever module seems affect display of app. namely, whenever run app using forever, login window styles changed , entire thing shifted left side of window. more, of app routes stop working. on other hand, whenever use simple npm start or nodemon command, works expected.

does know why may happening? how make server run continuously , not mess app itself?

p.s. may useful mention reason, app works upon running npm start , not work when node app.js run. unsure why happens.


Comments

Post a Comment

Popular posts from this blog

ssh - Vagrant Windows - ssh_exchange_identification: read: Connection reset by peer -

-
it seems can't ssh virtual box. i have virtual box running win7. host pc in win7. virtual box created through vagrant following vagrantfile. vagrant.configure("2") |config| config.vm.box = "http://aka.ms/vagrant-win7-ie11" end open cmd. go root folder of vagrantfile. execute following command: vagrant cmd displays: bringing machine 'default' 'virtualbox' provider... ==> default: clearing set forwarded ports... ==> default: clearing set network interfaces... ==> default: preparing network interfaces based on configuration... default: adapter 1: nat ==> default: forwarding ports... default: 22 (guest) => 2222 (host) (adapter 1) ==> default: booting vm... ==> default: waiting machine boot. may take few minutes... default: ssh address: 127.0.0.1:2222 default: ssh username: vagrant default: ssh auth method: private key timed out while waiting machine boot... time o...
Read more

gcc - Neither ld wrap nor LD_PRELOAD working to intercept system call -

-
i trying use -wl,-wrap=sendto -wl,-wrap,sendto in final g++ link command links app replace standard sendto function own. i compile following source code gcc -c -o wrap.o wrap.c , include wrap.o in final g++ command links app (the rest of app c++ hence use of g++) #include <stdio.h> #include <sys/types.h> #include <sys/socket.h> ssize_t __real_sendto(int, const void *, size_t, int, const struct sockaddr *, socklen_t); ssize_t __wrap_sendto ( int sockfd, const void *buf, size_t len, int flags, const struct sockaddr *dest_addr, socklen_t addrlen ) { printf("my wrap sendto ...\n"); return __real_sendto(sockfd, buf, len, flags, dest_addr, addrlen); } when use sendto in own source code, wrapper in fact used ok 3rd party shared objects linked against in final g++ command use sendto still use system sendto i.e. not wrapper. how can sendto wrapper used throughout ? i have tried ld_preload approach sendto , dlsym(rtld_nex...
Read more

maven - jacoco coverage per test setup -

-
i'm using jacoco in order gather code metrics , import them sonarqube missing details coverage per test. after searching came this tutorial failed make work on project. here pom.xml <properties> <sonarversion>2.4</sonarversion> <spring-framework.version>4.0.0.release</spring-framework.version> <spring-framework.security.version>3.2.5.release</spring-framework.security.version> <jackson.version>1.9.13</jackson.version> <jacoco.version>0.7.7.201606060606</jacoco.version> <aspectj.version>1.7.4</aspectj.version> <sonar.java.coverageplugin>jacoco</sonar.java.coverageplugin> <sonar.dynamicanalysis>reusereports</sonar.dynamicanalysis> <sonar.jacoco.reportpath>${project.basedir}/target/jacoco.exec</sonar.jacoco.reportpath> <sonar.jacoco.itreportpath>${project.basedir}/target/jacoco-it.exec</sonar.jacoco.itreportpath>...
Read more