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.
However, in the deploy.rb, I have the db role defined as web1 and that seems wrong if for nothing other than a readability issue. It seems this is a non-standard way of doing things, but I am not sure that there is a problem with it. What are the best practices here and given the current migration situation, how should the deploy.rb read? Regards, Christopher Wilson --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
