Hi,
I just did my first django deploy with nginx+fcgi with ssl and I have
to say it was much easier to set it up and configure it than nginx
+apache2+wsgi
It also uses way less ram and CPU then the other deploy. Also I am
using supervisord to manage the django fcgi.
So far very happy with it
lzantal
On Jun 24, 2010, at 2:54, Dave E <dever...@innotts.co.uk> wrote:
I'm about to enter my first deployment learning curve, but after
reading James Bennett's post 'Let’s talk about WSGI' (http://www.b-
list.org/weblog/2009/aug/10/wsgi/) and further procrastinating by
reading through a whole pile of (horribly varying) tutorials and WSGI
guides, I'd like to know:
1. what the Django deployment wisdom is for the near future?
2. whether it's really worth running lighttpd (or whatever) for static
files on small-scale sites (say, where there's just a blog and a few
rarely-altered pages)?
(My very small partnership runs Apache2 on a Linux VPS server (Debian
5.0.4/Lenny with 512 MB).
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To post to this group, send email to django-us...@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
.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@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.
