On Feb 8, 2008, at 1:11 PM, Jamis Buck wrote:
> Wasteful? Perhaps. But it's a lot more convenient for everyone > involved if you assume that you blast the entire app to all servers. > If that bothers you (and it might bother some people, and might even > bother them for valid reasons), then you are, of course, welcome to > write your own deployment tasks that pick and choose what gets > deployed where. Capistrano can make that easy. Right on. deploy:upload for the win. > If your database servers are off-limits, simply define one of your > app servers to be :primary => true in the :db role and be done with > it. A lot of people do it this way. In several architectures I've worked with recently there's been a "util" box that housed a gem server, an email server, some cron jobs, etc. This box is a good candidate for the :db role too. > I fully acknowledge that questions like these come up because of the > lack of documentation for Capistrano. I really, really apologize for > that. I think I speak for everyone here when I say "thank you Jamis" for all the hard work you've done on Capistrano. Yours, Tom --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
