On Thu, Mar 17, 2011 at 3:04 PM, maciekjbl <maciej....@gmail.com> wrote: > Ok ... so my main problem is that it's my first Django, Apache, Nginx > instalation ever.
I'd say keep it simple. specially on an intranet-only setup where you're unlikely to need the absolute maximum performance. the two-server advice is useful to prevent application RAM vs media cache fights. there are several setups that get you there. pick the one where you'll feel more comfortable. 1: the (old) two servers, one proxying the other. 2: mod_wsgi in daemon mode. this keeps the Python code in a separate process, giving the same advantages as the two-server mode, but all configuration is on apache.conf 3: FastCGI: sometimes overlooked, but it also keeps the (Python) app code on a separate process and the web-serving (with static media) on the frontend. The main drawback is that flup (like most FastCGI tools) won't help with dynamically adjusting the number of worker threads/processes to the load. in your case, i guess just doing apache + mod_wsgi is the easiest approach. you get a very good process management and keep the configuring in a single place (apache.conf). Handling static media in Apache won't impact negatively on your app. -- Javier -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
