A
A
Anton Medvedev2013-05-03 15:08:16
JavaScript
Anton Medvedev, 2013-05-03 15:08:16

Running multiple versions of a node.js app on the same server?

What is the best way to organize the work of several versions of one node.js application on a production server?
Run each application version on a separate port? Is there any way to automate this? How to raise this after restarting the server?
It would be ideal to have some kind of utility that would itself monitor the work of each version of the application based on the repository tags. For example, if you add a new tag - a new application instance, if you delete a tag - the application closes.
Perhaps there are already some tools for this?
Thanks in advance.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
M
Mithgol, 2013-05-03
@Mithgol

In order for the application to rise after (re)launching the production server, it is necessary to register its launch in some autorun script on this machine: it seems to me that humanity has not yet managed to invent anything better in this regard.
The question about tracking and restarting is answered in the Restarting and continuous running section on the Node modules wiki page . I don't see anything tracking repository tags there. At the most, keep track of the source files. No more.

P
pomeo, 2013-05-03
@pomeo

nodejs.org/api/cluster.html
How to raise link above from Mithgol , I used to use supervisor .

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question