>> >> If you run: >> svn propset svn:ignore mongrel_cluster.yml >> >> Then mongrel_cluster.yml will no longer be checked in/out.
Just be sure you setup an after_deploy task to write it out from a tracked copy otherwise you'll lose it the first time you deploy and wonder why you're site won't work... How do I know this? Uh... heh. :) >> >> - Mike >> >> -----Original Message----- >> From: rubyonrails-deployment@googlegroups.com >> [mailto:[EMAIL PROTECTED] On Behalf Of Raul >> Sent: Friday, March 23, 2007 8:24 AM >> To: rubyonrails-deployment@googlegroups.com >> Subject: [Rails-deploy] capistrano and mongrel_cluster.yml >> >> Hey everyone! Hope you guys are all doing good. >> >> I was wondering how anyone here might be handling their >> mongrel_cluster.yml >> file with capistrano on multiple environments. I have my team, 3 of us >> with >> our own local development environment, a test webserver with >> nginx/5mongrels >> and a pack of live servers with nginx/12mongrels each. I haven't finished >> my capistrano recipe yet but it looks to me like when I deploy it's going >> to >> overwrite all my mongrel_cluster.yml files on every machine, both test and >> production, with the same file. That would make things screwy. I want >> all >> the production servers to get the same yml file but the test one should be >> different. >> >> Thoughts? >> >> Raul >> >> >> >> >> >>> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
