For non-platform specific gems, we do, and I'd recommend freezing them into your codebase, that way you track them with your code, and they are simply there with your app - you never have to worry about the version on a machine being out of sync with what your app expects, etc. You can use Rick Olsen's gems plugin to make this easier: http://agilewebdevelopment.com/plugins/gems
For platform-specific gems, we haven't quite got this in yet, but we're planning to use the same/similar approach as is covered here (see down in the comments about the platform specific dirs): http://errtheblog.com/post/2120 On 6/4/07, crayz <[EMAIL PROTECTED]> wrote: > > > Anyone know of a way to automate gem installation/deployment? I'd like > to be able to add the installation of required gems to a kickstart > %post section, to get deployment down to: > 1) kickstart new machine w/ gems > 2) cap deploy to it > 3) no step 3 > > Currently there's a step 1.5 of having to go manually install a bunch > of gems, because some gems require you to specify the platform at an > interactive prompt - I can't see any way to specify it via a command > line argument > > A way to either kickstart the appropriate gems or have capistrano > deploy them would be amazing. I read about gem_server, but this > doesn't seem to help the platform selection issue > > > > > -- Chris Bailey [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
