Tim Ferrell wrote: > > I am in the process of migrating several rails apps from a single server > that runs nginx, mongrel, and mysql to separate (virtual) servers and am > wondering if I am, perhaps, overthinking my new deployment strategy. I > am using Capistrano 2.1, btw...
okay. I did the same thing, first rev of application was all on one, and second one was on seperate virtual servers, such that I could move them to additional hardware and/or add mongrel cluster machines. > What I would prefer is for the app tree to be deployed such that the > rails app stuff is only on the vm running the mongrels, the static files > would go to the nginx server (which is proxying to the rails backend) > and no files would get put on the mysql server... but this leaves me > with a few questions :-) so, cap does not seem to do this. I just lived with the fact that my ruby code exists on my web server, such that /public gets pushed out. Oh well. I didn't install mongrel or ruby on that machine, and it has no database passwords... > Is there an easier way to exclude files/folders from being deployed to a > role than just sending them and then deleting them? I am using the > copy+tgz strategy to update code to avoid the need for scm utils on the > production servers. I also realized that installing all of ruby/gem/etc. on my database server was silly. So, I don't list my database server role. The machine marked as the "db" role is the one which will run the migrations. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
