chwilson wrote: >Is there a compelling reason to run the db migration from the db >server? We currently like to keep that particularly box as stock as >possible and don't have ruby, rake, cap installed there. We run the >migrations from web1. > I was also puzzled by this, since the standard Rails approach is migrations run from a place where the application is deployed, i.e. the app server. If you generalize your thinking about Capistrano as a deployment tool, of which Rails is one use, this begins to make a little more sense.
There is no way we would be permitted to deploy application code on the database servers (which are managed centrally). I have done close to what you suggest, namely assign one of the app servers to the db role. So really the db role goes to a machine that can connect to, and run migrations against, your database. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
