What happens exactly when the node.js application is hot installed on Openshift?

Question

From the documentation I could find, I don’t understand what exactly happens when the application is node.jshot deployed in Openshift.

Are the following assumptions correct?

• Existing application node.jsstopped.
• A new application is launched node.jswith the new code pressed.
• Everything that was in the memory of an existing application node.jsis not transferred to a new one.
• If these applications use a database (in another cartridge), this database does not restart. An existing application closes its connection, and a new application creates a new one.
• Consequently, hot deployments are not recommended if you need to run the script database needed for your new pushed code node.js.

Answer 1

I think the best way to answer this question is to go to the source.

The post_deploy management operation used as part of the build life cycle (git commit) is called a call.

, ( npm, ), -. NPM, , , . , , NPM , , , documentation.

, .

Answer 2

- openshift, , lines ,

, , - , this

, js , , js, js . , . , , , .

, openshift , ( , ). , :

• node.js node.js :

• ( ), . , :