You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.
Basically, when I create a new Node.js application, changes done even to static content (such as .html, xhtml pages etc.) are not shown until I restart server. So all rsynced changes won't get effect until I restart it. There is a official way to develop and that is setting up DEV_MODE environment variable to true, which enables nodemon to check changes and restart application. Because there is almost zero turnaround for restarting Node.js application, I think it would be good to have DEV_MODE set to true by default to allow users modify their applications out of the box - without any need to add environment variable to deployment and respin application pod.
Basically, when I create a new Node.js application, changes done even to static content (such as .html, xhtml pages etc.) are not shown until I restart server. So all rsynced changes won't get effect until I restart it. There is a official way to develop and that is setting up DEV_MODE environment variable to true, which enables nodemon to check changes and restart application. Because there is almost zero turnaround for restarting Node.js application, I think it would be good to have DEV_MODE set to true by default to allow users modify their applications out of the box - without any need to add environment variable to deployment and respin application pod.
See also https://issues.jboss.org/browse/JBIDE-22362 for more reference to this issue.
The text was updated successfully, but these errors were encountered: