If the second app is a rails app, why should you have any migrations at all?
If it's not, is it possible to create a schema_info table for rails? And if Rafael is right about deploy:cold, you could always just manually do deploy:update and deploy:start. I know we often have to do a bit of manual work on the first deploy -- there's always a migration somewhere that depends on a plugin that we're no longer using... On Mon, Apr 7, 2008 at 9:12 AM, Lucas <[EMAIL PROTECTED]> wrote: > > The database in my RoR application is shared with a 2nd application, > and created by the latter, so I need capistrano (cap deploy:cold) to > assume the database is there and ready to use already, instead of > trying to run all migrations. Is there a way? Should I create an extra > task? > > thanks > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
