On Fri, 2007-06-08 at 00:38 +0800, Nimrod A. Abing wrote: > Hello, > > I am currently doing research on scaling one of the sites I made using > Django. I have looked at Chapter 21 of the in-progress Django Book. I > plan to follow the track recommending 3 django servers behind perlbal > + 1 dedicated media server + 1 dedicated database server. > > The current setup for the site I am working on uses a single machine > for the whole site. I have Apache + mod_python on one IP address > serving Django requests. For media, I have lighttpd running on another > IP address on the same machine. Postgresql is also running on the same > machine. > > This site allows users to upload pictures. Those uploaded pictures are > then served by lighttpd. While this works quite well in our single > machine setup I am dumbfounded as to how to handle file/image uploads > when we finally move to a load-balanced setup with a dedicated media > server. > > The only thing I can think of right now is to share a directory on the > dedicated media server and have each server in the Django cluster > mount that share either through NFS or Samba. But I don't think it's a > good idea to do it this way.
Or just copy the images across to the target machine. You could either do this as part of your model's save() method or initially store them on the Django server and have a cronjob periodically copy them across to the analogous directory on the image server. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
