On Thu, Jun 12, 2008 at 7:45 AM, John Trupiano <[EMAIL PROTECTED]> wrote: > This is, in fact, the same idea Rick mentioned that I proposed. I > suggested moving gem configuration out into a YAML file (or at least > adding a hook for this). Why? Because then capistrano could read in > that file and ensure that deployment environments have the proper > versions of gems, etc. In other words, I could stop a sure-to-fail > deployment before I actually re-deploy. (There's a lot more to this, > but not so much core-related) I had proposed a config extension along > the lines of: > > config.gem_file "config/gems.yml"
Totally off topic at this point, sorry, but anyway... John and I hacked on this a bit this morning. The conclusion is that there is no reason to do what he said above. GemInstaller.autogem already does everything you want if you desire to manage your gems from YAML. See: http://geminstaller.rubyforge.org/faq.html#rails_config_gems http://geminstaller.rubyforge.org/documentation/tutorials.html#integrating_geminstaller_into_ruby_on_rails Thanks! -- Chad --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@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-core?hl=en -~----------~----~----~----~------~----~------~--~---
