On Thu, Apr 5, 2012 at 1:25 AM, Pedr Browne <[email protected]> wrote:
> Would you mind elaborating on the these option? This is new ground for > me. I haven't used SSL before and I've never set up a production > server. It's common to use a web server like Apache httpd that can listen on multiple ports, e.g. both 80 (http) and 443 (https) and proxy requests to a back-end Rails server like thin, mongrel, unicorn. It's not hard to configure and there are plenty of tutorials, I'm sure. (You can also use nginx, squid, or some other proxy.) And some people use Passenger (mod_rails) which gives you an integrated Rails server with Apache httpd or nginx, eliminating the backend/proxy part. Less flexible but fewer moving parts... Either approach will work in production, so I'd look into both and see what feels best to you. -- Hassan Schroeder ------------------------ [email protected] http://about.me/hassanschroeder twitter: @hassan -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
