Re: Deployment hesitation after James Bennett's post, WSGI or ...?
On 24 Jun 2010, at 12:15, Daniel Rosemanwrote: > On Jun 24, 10:54 am, Dave E 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? > > WSGI. Absolutely no question about it. > >> 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)? > > No, not really. For that setup, a single Apache instance is fine. > >> (My very small partnership runs Apache2 on a Linux VPS server (Debian >> 5.0.4/Lenny with 512 MB). > For this kind of setup I can really recommend going with nginx + fcgi or gunicorn. Do you require Apache for other parts of your setup? If not then it is worth considering getting rid of it. > -- > DR. > > -- > 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
On Jun 25, 2010, at 1:55, Dave Ewrote: I'll certainly share my observations. 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. That's a great alternative, especially when VPS memory is costly. Since I love condensing lengthy instructions to the absolute minimum, and Django deployment guidelines are all - well - wordy, how about writing that up somewhere? If you have time, that is :-) I sure will once I get around it and get some free time:) I can also use a write up for my own documentation so it will happen for sure. I am running a satchmo store with 4300+ product on it using virtualenv. lzantal -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
Hi, WSGI is the best option. For that we're using ngnix+cherrypy (just the wsgi adapter) and it works like a charm. Recently we've start testing gunicorn as well, as the deployment is really easy. This kind of configuration allows you to reduce drastically the memory consumption, so you can deploy small applications on cheap vps. But programing Django is addictive and for sure you'll finish with a dedicated server :) Best regards, -- Antoni Aloy López Blog: http://trespams.com Site: http://apsl.net -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
I'll certainly share my observations. > 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. That's a great alternative, especially when VPS memory is costly. Since I love condensing lengthy instructions to the absolute minimum, and Django deployment guidelines are all - well - wordy, how about writing that up somewhere? If you have time, that is :-) -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
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 Ewrote: 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
On Thu, Jun 24, 2010 at 5:04 PM, Dave Ewrote: > Thanks for all that. I'm going to: > > 1. go with a standard mod-wsgi setup in each Django site's VirtualHost > container and check performance, > > 2. then look at Gunicorn, > > 3. then assess whether running another server for static files is (for > my sites) worth it. > (while testing, I'm delivering static files locally - in a > designated directory - but directly from Apache.) > > Do share your observations after that ;) -V- http://twitter.com/venkasub -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
Thanks for all that. I'm going to: 1. go with a standard mod-wsgi setup in each Django site's VirtualHost container and check performance, 2. then look at Gunicorn, 3. then assess whether running another server for static files is (for my sites) worth it. (while testing, I'm delivering static files locally - in a designated directory - but directly from Apache.) - Dave -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
On Thursday 24 June 2010 15:24:32 Dave E 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? wsgi > > 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). > for a small vps, nginx with fcgi is a very good option (or cherokee I'm told) -- Regards Kenneth Gonsalves Senior Associate NRC-FOSS at AU-KBC -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
On Jun 24, 10:54 am, Dave Ewrote: > 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? WSGI. Absolutely no question about it. > 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)? No, not really. For that setup, a single Apache instance is fine. > (My very small partnership runs Apache2 on a Linux VPS server (Debian > 5.0.4/Lenny with 512 MB). -- DR. -- 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.
Re: Deployment hesitation after James Bennett's post, WSGI or ...?
Hi, On 2010-06-24 11:54:32 +0200, Dave E said: 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? No idea, but i started to use Gunicorn (via django-unicorn) recently. It's easy to deploy and fast. http://gunicorn.org/ 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)? Yes, of course. Why not? Kai -- 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.