similar to: request.ssl? not working

I''ve been hunting the web and reading the mailing lists all day but I''m not finding any guidance on this problem. When I try to talk to my mongrel it simply responds with NOT FOUND and nothing else. I can''t find anything on google because this has to be the second most commond phrase in existence. Any help or guidance would be greatly appreciated. Sincerely, Chuck Vose

I''d like to use Mongrel_cluster with SSL on a green-field application (it can be configured however is best - initially, "ease of setup" is important, but then soon after will be scaling and response time). I''ve read a lot of emails on this topic, and checked out the Mongrel pages, etc, but I''m left with this question of what is recommended: For a

I have a small intranet app with only 20 or so users. I''m currently using lighttpd w/ssl for production and mongrel for dev. I don''t think Mongrel supports ssl, but what is the easiest front-end to put in front of it? Pound? Thanks Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century

Hi all, I''m currently trying to get Mongrel running my app whilst fronted by apache 2.2 in a sub-directory via https. A bit convoluted I''ll grant you but necessitated by existing systems. The pertinent parts of my httpd.conf: <VirtualHost 123.123.123.123:12345> #historic choice of random port number DocumentRoot /var/www/admin ServerName admin.example.com:12345

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even

I''m setting up a new server in anticipation of switching from lighttpd+fcgi. My application isn''t completely imported yet, so I don''t expect it to work. For instance right now when pulling up my app from localhost I get my Ruby/Rails MySQL error message. But when I pull it up from a remote computer I get a proxy error from Apache: ====================== Proxy Error

more info just 1 server webserver + appserver + dbserver On 9/14/07, Yan Meng <dreamwords at gmail.com> wrote: > > Hi, Guys > > Our team is running a web2.0 finance site in China > > http://www.caibangzi.com/ > > We use APACHE + mod_proxy_balancer + mongrel to deploy our application, it > workd super in the past few monthes. > > However, just from last

I''m trying to setup a mongrel cluster. I''m relying on information collected from a number of sources but I''m relying heavily on http://mongrel.rubyforge.org/docs/apache.html. I have noted that a number of sources mention the necessity of having the mod_balancer module installed in Apache. However, my primary source makes no mention of this; but instead, mentions only

Hello list, I wonder if someone could help me understand the following: I''ve got a managed dedicated server with GoDaddy. Until now, I''ve only hosted PHP applications there. I now need to set it up to host my new beloved Rails application. I asked them to set up apache with mod_proxy_balancer for the mongrel cluster, however, here''s what they told me: *Unfortunately,

I''m trying to do some initial benchmarking of our setup, mainly just to establish baselines. I''m essentially using the process Zed outlines in a previous message: http://rubyforge.org/pipermail/mongrel-users/2006-May/000200.html What I''m running into is that Mongrel appears only half as fast as Apache when serving a small static HTML file. If I then add in Apache with

> On 5/23/06, Walter <Walter at mwsewall.com> wrote: > [...] > > I realize that mongrel is not thread safe, I was hoping mongrel might > spawn a few processes and serve them in the background to emulate what I > wanted. > > > > Rails is not thread-safe. > Yes, that?s what I meant. <snip> > > The idea of the BackgroundDrb is that you perform

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

Hello everyone- I am considering using Mongrel and I have read this list pretty extensively. I know that the Apache/mod_proxy_balancer/mongrel approach is the preferred one right now, with Apache serving the static content via mod_rewrite and such. However, in my hardware arsenal, I already have an old and trusty LocalDirector, which I would be inclined to at least try first as a

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Gang- We are getting ready to launch our ROR application; the last item remaining is the deployment platform. For testing, we had used Apache + MOD_FastCGI. I am not that impressed with it; sometimes it has strange effects. For example, when we start the application, for about 5 minutes or so, the app is very unstable and it gets better over time. My questions is .. should I go with (1)

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

A couple of questions please: What is the benefit of having more than one Mongrel/Rails instance on the same machine, could one instance not serve as many requests as say three instances? Is Mongrel Cluster a Apache add-in (like mod_*) or a separately running load balancer which runs on a separate port, I could not work it out from the sample Apache config... |# Redirect all non-static

Is anyone using ferret with Mongrel/Mongrel-cluster? The first one or two times I access the ferret index it works fine, but then it throws a write lock error StandardError (: Error occured at <index_rw.c>:703 Error: exception 6 not handled: Could not obtain write lock when trying to write index ): I need to do more testing on this to narrow down the problem/solution but just wanted to