Thanks for responding... ./vendor is committed, and it gets pushed.
$ svn st -u Status against revision: 798 $ rake rails:freeze:gems (in /x/home/username/projects/rails/my_app) Freezing to the gems for Rails 2.0.2 Unpacked gem: 'activesupport-2.0.2' Unpacked gem: 'activerecord-2.0.2' Unpacked gem: 'actionpack-2.0.2' Unpacked gem: 'actionmailer-2.0.2' Unpacked gem: 'activeresource-2.0.2' Unpacked gem: 'rails-2.0.2' $ svn st ~ vendor/rails I think I only did rake rails:freeze before...not sure the impact of this, but the "~" in svn status seems odd. '~' versioned item obstructed by some item of a different kind. Any ideas how to properly push with the gems, rails, etc. that I'm using on my local box? I have not actually pushed in this state yet...as it seems to be in disarray. On Fri, Jun 13, 2008 at 12:38 PM, John Trupiano <[EMAIL PROTECTED]> wrote: > > Are you deploying from an SCM? If so, did you remember to commit your > vendor directory before re-deploying? > > -John > > On Jun 13, 3:22 am, "Anthony Ettinger" <[EMAIL PROTECTED]> wrote: >> Do prod gems get ignored when I do a rails --freeze locally before I push? >> >> -- >> Anthony Ettinger >> 408-656-2473http://anthony.ettinger.name > > > -- Anthony Ettinger 408-656-2473 http://anthony.ettinger.name --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
