Re: [Radiant] Freezing Gems?
Erik Ostrom said the following on 12/03/2008 02:35 AM: Hm. Since there isn't a clear standard for freezing gems, sometimes they need some coaxing. I'd try running it either (a) on a machine you have more control over or (b) on Mongrel, to try to get some more diagnostic logging. ... Okay, I've just tried freezing RedCloth 4.1.1 into my Radiant app at home. I got a Phusion error about a missing RubyGem echoe, installed and froze that, and now my app works. So if you didn't get echoe already, you could try that. Otherwise I don't know. Dreamhost is a hosted site, so the machine you have more control over isn't a fair test. I can't cotnrol the Passenger configuration and I'm stuck using the local GEM_HOME in ~/.gems I can't install gems in /usr/lib/ruby since this is a hosted service and when I point out that all I'm working with uses gems from the standard Ruby Gems repository Dreamhost support tell me its custom software and unsupported and when I point out that many of their gems are out of date they tell me they can't update until all the new ones have been tested. Apart from this incident Dreamhost have always been very supportive but this 'denial' and 'blame the user' is getting me very frustrated. -- It is impossible for a man to begin to learn what he thinks he knows. -- Epictetus ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Freezing Gems?
On Tue, Dec 2, 2008 at 6:37 PM, Anton J Aylward [EMAIL PROTECTED] wrote: Erik Ostrom said the following on 12/02/2008 07:46 PM: I'm hosting a site with Passenger on Dreamhost - it's slow, but functional. I used Dr. Nic's Gems on Rails plugin: http://gemsonrails.rubyforge.org/ Basically, you install Gems on Rails as a Rails plugin; install your gems in the normal way; then use 'rake gems:freeze' to install them in vendor/gems in your application. Seems to work fine with Radiant/Passenger/DreamHost. Hmm. Now it blows up with a phusion message: The application has exited during startup (i.e. during the evaluation of config/environment.rb). The error message may have been written to the web server's log file. Please check the web server's log file (i.e. not the (Rails) application's log file) to find out why the application exited. the error log file has no entry at the time for my IP address and the access as only the request that I expect to see. No diagnostics. I suspect it blowing up at the line in evironment.rb that reads config.plugins = [ :all ] though I'm not sure how I can prove that. What else did you do? Unfreezing the gem (RedCloth-4.1.1) and the application works once again Next! Does the RedCloth 4.1.1 gem need to be compiled? If so, and you are freezing it, it needs to be compiled on the same platform and OS as whatever Dreamhost is using. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
