Ugh, I actually ran with NFS for a couple of months but I was losing sleep at night wondering if it would keep on chugging along.
The other thing you can do is just set up one more reliable webserver (better yet, two in a cluster, load balanced) as your asset server, deploy a copy of your public folder there and make all your uploads write to that server. I also toyed with the idea of file replication amongst all my web servers but having never done it I was reluctant to give it a go. Hopefully one or some combo of these will give you some inspiration to do what I haven't. :) Raul ----- Original Message ----- From: "Tim Ferrell" <[EMAIL PROTECTED]> To: <rubyonrails-deployment@googlegroups.com> Sent: Thursday, June 19, 2008 10:17 AM Subject: [Rails-deploy] Re: nginx/mongrel with multiple machine deployment > > Raul wrote: >> I have a similar setup and what I did was open an Amazon S3 account and >> use >> attachment_fu to push the uploads to it. So my servers can access it all >> from a single point now. >> > > Thanks Raul - not a bad idea, but unfortunately not an option with this > app, due to some other restrictions that limit me to a local filesystem. > > Any other ideas? > -- > 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 -~----------~----~----~----~------~----~------~--~---
