Here is some description of situation that I was in. The rails app is not mine and I had just to deploy it for the proof of concept demonstration. The mod_rails was my natural choice. The folder privileges are set as they should be. Since that is on a VPS I have noticed the long first hit response time due the spawn process. That was expected but it was a bit to long for me. Then I noticed that there is no mod_deflate and I include it too and it was a bit better but cold start up was still to long.
Than I noticed that javascript_include_tag can be changed by adding the :chache=>true directive since it was in production environment. At first it helps and app becomes more responsive. Then the second time I have start the whole system again at first I have got a 503 and on a second request everything is working OK. This was repeatable on every first spawn hit. For some reason I try to check to see what the all.js is looking and noticed a strange message from a firebug that this file is missing. Then I requested just the all.js from the browser and the same result – 404. Even to my biggest surprise no message in production log or apache logs except ones for 404. Since I was on a tight schedule the solution was: go with the known. Just fire up a mongrel, witch was not present at the time of previous test, and width plain vanilla setup. Everything was working right of the box, the all.js was present and response time on first hit was as expected. I will try to make the same situation again ASAP to be able to go little deeper in. If I find some new light on the case I’ll post it. The mod_rails is a good solution for fast deployment and it’s much easer to educate people to use it. On Sep 30, 12:22 am, "Xavier Noria" <[EMAIL PROTECTED]> wrote: > On Mon, Sep 29, 2008 at 10:51 PM, dima <[EMAIL PROTECTED]> wrote: > > The second thing that wasn't running was javascript_include_tag > > with :cache=>true. > > What do you mean? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
