From: Dylan Stamat <dstamat@elctech.com>
To: mongrel-unicorn@rubyforge.org
Subject: re: multi server failover setup
Date: Mon, 26 Oct 2009 12:34:00 -0700 [thread overview]
Message-ID: <E31C66B5-7ECF-4B34-8F37-B49440EC7BBD@gmail.com> (raw)
Eric, have you heard of anybody using the idea you laid out here?
http://article.gmane.org/gmane.comp.lang.ruby.unicorn.general/31
I really like the approach, and hoping I'm not going to be the first
one trying it ;)
I noticed that Mr. Wanstrath is using UDS in his deployment here: http://github.com/blog/517-unicorn
Wondering if they're running with the same or similar strategy as your
suggestion?
Our application is long-running-request heavy, so we may actually be a
Rainbows! candidate.
Thanks!
==
Dylan
next reply other threads:[~2009-10-26 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 19:34 Dylan Stamat [this message]
2009-10-26 19:42 ` multi server failover setup Chris Wanstrath
2009-10-26 21:42 ` Eric Wong
2009-10-26 21:47 ` Chris Wanstrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E31C66B5-7ECF-4B34-8F37-B49440EC7BBD@gmail.com \
--to=dstamat@elctech.com \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).