Hi Anibal, Thank you for joining the thread. A follow-on question below.
Aníbal Rojas wrote: > As I undertand the ruby-mysql library 2.7 does require the > libmysqlclient to be properly installed, and depending on > the location of mysql.so it is possible that rubygems is unable > to load it, while the library is actually using it... I've had other problems with this environment and its beginning to feel like maybe they're all symptoms of one underlying, probably simple, cause. The first involved BackgroundRb. Even though I had the line in environment.rb uncommented to set RAILS_ENV to production, BackgroundRb was not picking it up and was writing the record of database access that I do in my worker to development.log. Invoking BackgroundRb with 'RAILS_ENV=production /script/backgroundrb/start -d' corrected that. But I'm still concerned because I have no idea why the behavior occurred in the first place. Is it possible the two behaviors are both related to some underlying problem? Thanks! Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
