Re: static on separate what?
running the media off a non-standard port without a front-end proxy to make it "look" like it's coming from somewhere on Port 80 may get you some trouble. In particular, we found that a lot of folks behind firewalls and in corporate environments simply didn't get anything on the media server *unless* we were shipping it out from Port 80. damned annoying - ain't right and all that, but there it is. -joe On Dec 9, 2007 1:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On Dec 9, 2007 3:07 PM, andy baxter <[EMAIL PROTECTED]> wrote: > > Does this mean running the django server on a different port to the > > static files, or is there a way to do it through virtual hosts? > > > > If you only have one IP, you could run media off a non-standard port. > If you have multiple IPs, just bind your media server to a different > IP (but still port 80). > > > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: static on separate what?
On Dec 9, 2007 3:07 PM, andy baxter <[EMAIL PROTECTED]> wrote: > Does this mean running the django server on a different port to the > static files, or is there a way to do it through virtual hosts? > If you only have one IP, you could run media off a non-standard port. If you have multiple IPs, just bind your media server to a different IP (but still port 80). --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: static on separate what?
James Bennett wrote: > On Dec 8, 2007 10:57 PM, Carl Karsten <[EMAIL PROTECTED]> wrote: > >> I this text, does "separate Web server" contingent on a 2nd box? If it is >> only >> one box, the same Apache instance would be preferred, right? >> > > No, and no. > > You don't have to have separate physical machines, but the recommended > setup is to have separate instances of whatever HTTP daemon you > prefer. The reason for this is that it's a gross waste of resources in > many cases to have a server process loaded up to serve requests > through Django, and then use that process for nothing more than > reading a file off disk and sending it down the wire -- you're tying > up a valuable and limited resource when you do this. Running a > separate instance of the HTTP daemon whose sole job is serving files > off disk (and possibly a different HTTP daemon, as not all such > daemons are created alike or optimized for the same use patterns) > frees up that valuable resource to do nothing but serve requests > through Django. > Does this mean running the django server on a different port to the static files, or is there a way to do it through virtual hosts? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: static on separate what?
On Dec 8, 2007 10:57 PM, Carl Karsten <[EMAIL PROTECTED]> wrote: > I this text, does "separate Web server" contingent on a 2nd box? If it is > only > one box, the same Apache instance would be preferred, right? No, and no. You don't have to have separate physical machines, but the recommended setup is to have separate instances of whatever HTTP daemon you prefer. The reason for this is that it's a gross waste of resources in many cases to have a server process loaded up to serve requests through Django, and then use that process for nothing more than reading a file off disk and sending it down the wire -- you're tying up a valuable and limited resource when you do this. Running a separate instance of the HTTP daemon whose sole job is serving files off disk (and possibly a different HTTP daemon, as not all such daemons are created alike or optimized for the same use patterns) frees up that valuable resource to do nothing but serve requests through Django. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
static on separate what?
I this text, does "separate Web server" contingent on a 2nd box? If it is only one box, the same Apache instance would be preferred, right? http://www.djangoproject.com/documentation/modpython/ === quote === Django doesn’t serve media files itself; it leaves that job to whichever Web server you choose. We recommend using a separate Web server — i.e., one that’s not also running Django — for serving media. Here are some good choices: * lighttpd * TUX * A stripped-down version of Apache If, however, you have no option but to serve media files on the same Apache VirtualHost as Django, === end quote === Carl K --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
