Re: Deployment hesitation after James Bennett's post, WSGI or ...?

On 24 Jun 2010, at 12:15, Daniel Roseman wrote: > 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- >>

Re: Deployment hesitation after James Bennett's post, WSGI or ...?

On Jun 25, 2010, at 1:55, Dave E wrote: 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

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

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

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

Re: Deployment hesitation after James Bennett's post, WSGI or ...?

On Thu, Jun 24, 2010 at 5:04 PM, Dave E wrote: > 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

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

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

Re: Deployment hesitation after James Bennett's post, WSGI or ...?

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

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

Deployment hesitation after James Bennett's post, WSGI or ...?

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.