I'll go with unicorn then. Apparently it handles more requests/sec
than Thin. But that might be old benchmarks who knows.
Sounds great - my sites are the same setup, but with regular thin. :)
All I ask is that it avoids sentences such as this one (from Unicorn):
"Slow clients should only be served by placing a reverse proxy capable
of fully buffering both the the request and response in between
Unicorn and slow clients."
Embarrassing to admit it and I'm going to look like a dumbo here, but
I don't really know what a reverse proxy is. I hate messing with my
servers (ancient Ubuntu and not-so-ancient Debian, running Apache) any
more than absolutely necessary. So I wouldn't understand how to apply
the information in that sentence, or - more crucially - whether I can
ignore it for a site(s) with small-to-modest traffic.
The Thin site does a nice, minimal job of explaining how to get things
running, but I'll be the first in line to watch the deployment
screencast and get Unicorn installed.
After trying to teach this stuff to complete beginners and failing,
what I'm saying is: don't take any server-related knowledge for
granted when explaining deployment - this is where a lot of frameworks
fall down - I spent *days* trying to get one server configured just to
run something simple (okay, that was Django and mod_wsgi - sshhh - but
the same kinds of hoops still need jumping through).
I guess the bigger difference would be hooking one of the Rack
servers to Apache instead of Nginx. But I think Nginx is a better
option since it's ment to serve static pages and Unicorn will be the
one handling all the dynamic stuff.
...but please include an Apache-only setup for those of us who haven't
installed Nginx (and really should, but just... haven't) and have very
modest loads, and a stack of legacy sites to run.
the "simple dumbest" build will launch the webserver with thin
(camping --port 80)
Nice'n'simple, but (if starting out and watching a screencast) I'd
want to a mention of what dependencies need installing on my server to
even get that far... I'm carrying on as dumb here because even getting
SQLite running on my old Ubuntu server (for a default Camping setup)
took some fiddling. SO maybe a quick: "here's how to check you have
SQLite running on your web server: `which sqlite3` or `sqlite3` then
from the sqlite shell `.quit`".
DaveE
this is what Unicorn sounds like: http://d.pr/olau
LOL! Now I know. These little asides are what keep me in this
community, and _why I came here in the first place.
_______________________________________________
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
