From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: rainbows deployment.
Date: Wed, 24 Mar 2010 11:51:58 -0700 [thread overview]
Message-ID: <20100324185158.GA4797@dcvr.yhbt.net> (raw)
In-Reply-To: <7E4A0A2E-7232-463B-A8D1-5F9BB32E3B6B-Nf+wZpSdgweeYOMve9Zru9BPR1lH4CV8@public.gmane.org>
Christoph Sturm <me-Nf+wZpSdgweeYOMve9Zru9BPR1lH4CV8@public.gmane.org> wrote:
> Hey rainbows peeps!
>
> in a deployment scenario, do i run rainbows behind nginx like unicorn,
> or is the best scenario to run it without?
Hi Christoph,
I do both, depending on the situation. As I've developed more
confidence in Rainbows!, I've found it easier to manage/hand-off apps
with Rainbows!-only deployments as there are fewer moving parts to deal
with.
Static file performance is acceptable with Rainbows! for most
situations, however it's unlikely to ever be as fast as nginx/lighttpd
for static files.
I'd love to hear other people's deployment experiences with Rainbows!,
too.
> our app has pretty short requests, we use rainbows mainly to get an
> eventmachine loop.
Give it a shot, it's more than likely to work. EM is very scalable and
handles slow connections very well.
--
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying
prev parent reply other threads:[~2010-03-24 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 15:11 rainbows deployment Christoph Sturm
[not found] ` <7E4A0A2E-7232-463B-A8D1-5F9BB32E3B6B-Nf+wZpSdgweeYOMve9Zru9BPR1lH4CV8@public.gmane.org>
2010-03-24 18:51 ` Eric Wong [this message]
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/rainbows/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100324185158.GA4797@dcvr.yhbt.net \
--to=normalperson-rmlxzr9ms24@public.gmane.org \
--cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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/rainbows.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).