@Brian: that looks awesome. i'll try it out next week. @Jacob: i guess i wasn't exact in my explanation. what i want in fact is a notification-based mechanism. like fleet or amino deploy/drone. fleet uses git under the hood. amino seems to use npm to package and request to deployment.
Am Donnerstag, 24. Januar 2013 23:31:46 UTC+1 schrieb Brian Link: > > Published my slides to http://cpsubrian.github.com/amino-nodedc > > On Thursday, January 24, 2013 4:51:52 PM UTC-5, Brian Link wrote: >> >> I just did a presentation at Node.DC on this very topic, so you can >> checkout my demos and slides. Demo-2 shows you how to launch a few drones >> and deploy to them. >> >> https://github.com/cpsubrian/amino-nodedc/tree/master/demos/demo-2 >> >> On Thursday, January 24, 2013 4:49:13 PM UTC-5, Brian Link wrote: >>> >>> We build and use a toolkit call Amino that satisfies a number of your >>> requirements. We also used fleet and seaport for a while, but eventually >>> progressed towards our new approach. >>> >>> http://github.com/amino >>> >>> You'll want to look at amino-drone and amino-deploy, which can get you >>> started deploying code to multiple physical machines. >>> >>> The docs aren't totally finished yet, but if you're serious about giving >>> it a go, let me know and I'll help however I can. >>> >>> On Thursday, January 24, 2013 8:01:20 AM UTC-5, greelgorke wrote: >>>> >>>> Hi folks, >>>> >>>> im searching for tools, which help me with this task. we have several >>>> modules out there for managing nodes clusters, but i haven't found much >>>> about managing application nodes based on different machines. I tried >>>> substacks fleet, and it's working ok, but it have several flaws in it. i >>>> searched fo some alternatives but haven't found any yet. another >>>> alternatives are using technics borrowed from other ecosystems like >>>> capistrano-based deployment etc. i just don't want to install tools based >>>> on other plattforms, wanna stay minimalistic in system requirements, so >>>> node + native shell/ubuntu tools would make me happy. the requirements: >>>> >>>> - deployment from a git repo, configurable branch (fleet does it, but >>>> works only from master) >>>> - rewinding to previous state with a single command (fleet versions >>>> deployments, fall back to previos state is done by spawn a specific commit) >>>> - starting, stopping, monitoring and keep alive all application nodes >>>> in the server-cluster from a single machine, no need to login to other >>>> servers >>>> - notifications about restarts, crashes and further health messages >>>> >>>> what are your strategies there? any known tools? >>>> >>>> cheers >>>> >>> -- -- 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
