> 1. Frontend-Proxy and static file server (i.e. Nginx od lighttpd) > if URL matches local file or rule: serve it > else: request file from Backend-Server (i.e. Apache) > 2. Backend Server > handle urls as in urls.py or your resolving strategy and serve > dynamic Data accordingly. > > In this way your Hostname is always the same. All Static files can be > served from your frontend-proxy with X-Accel-Redirect even private > data. You also can serve cached dynamic content directly from your > proxy without hitting the apache. > > In larger setups the frontend-proxy also can handle the load-balancing > stuff.
Well that's about a foot and a half past my current server configuration abilities, but I appreciate the direction, and I'll start doing some reading! If you or anyone has any more resources you can point me towards, I'd be grateful. Thanks, Eric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
