if these are all different services listening on different ports and doing different things then i don't think cluster or "up" will be much use to you. you should just be able to use the child_process bindings in node.js to spawn each of the separate processes from a master process and listen for the exit events on each child process and respawn them when it fires.
On Tuesday, April 3, 2012 11:17:14 PM UTC+1, JGAui wrote: > > I've got a site that has many components that need to run on > deployment (web server, email service, photo resizer service, various > jobs, etc) and I was wondering how others handle this scenario. > > My initial thought was to have a master cluster that forks off all of the > separate processes. I'd put the master process in something like upstart > to make sure that it kept running and ideally I'd build some logic in the > master to be able restart the child processes and to gracefully restart > when I need to push new code. > > I've also looked into up (https://github.com/LearnBoost/up), but haven't > played with it yet. > > Does anybody have any suggestions? > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
