Django in production on Windows

Hi Anthony,

I was in a situation similar to yours not too long ago - introduced Djangoat work and we've enjoyed it. We are getting better time to market than wewould with other options (PHP, .NET etc). Also, coding in Python has beengreat fun.So, good choice.

As to your question, I have no experience running Django on Windows otherthan using the development server. I think that you'd be best off findinggood Linux hosting - WebFaction, Linode etc.

Some links that may help:http://djangofriendly.com/hosts/http://djangohosting.org/Regards,Lloyd

-- Regards,Sithembewena Lloyd Dubehttp://www.lloyddube.com-- 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 athttp://groups.google.com/group/django-users?hl=en.

Django in production on Windows

I developed Djano on a windows server and everything went smoothlyexcept getting it to work with IIS. I loaded apache on windows and itworks great.

On Dec 1, 6:43 am, ashdesigner <antony.shash...@gmail.com> wrote:> Hello,>> I am absolutely new to Python/Django. Being responsible for a large> corporate startup project and having looked through a number of MVC/> MVT frameworks I decided to outsource the webproject in Django.>> The only undiscovered issue to us is whether we can launch a heavy> loaded website in Django under Windows (IIS) + MSSQL. Would appreciate> any comment please.>> Anthony

Django in production on Windows

Hi Lloyd,

Thank you so much for your reply. You see, the new project is stillcurrently regarded of as probationary, though the choice of the Djangoframework is agreed and seems to be confident.

The issue is that we will be running a separate VPS for the project,and Windows+IIS+MSSQL perfectly suits our current administrationfacilities. In other words, we would prefer adminstrating Win+IISrather than Unix+Apache or whatever. Nonetheless, I can't affordmaking wrong choice of the platform so I need advice from a realpractice.

Django in production on Windows

Pete,

Does this mean that we shouldn't even try to run it on IIS7 inproduction?

On Dec 1, 4:27 pm, CrabbyPete <pete.do...@gmail.com> wrote:> I developed Djano on a windows server and everything went smoothly> except getting it to work with IIS. I loaded apache on windows and it> works great.>> On Dec 1, 6:43 am, ashdesigner <antony.shash...@gmail.com> wrote:>> > Hello,>> > I am absolutely new to Python/Django. Being responsible for a large> > corporate startup project and having looked through a number of MVC/> > MVT frameworks I decided to outsource the webproject in Django.>> > The only undiscovered issue to us is whether we can launch a heavy> > loaded website in Django under Windows (IIS) + MSSQL. Would appreciate> > any comment please.>> > Anthony

Django in production on Windows

Hi Antony, it's a pleasure.

Regarding your last question - I am sure you could get a Django/ IIS7 setupto work,but I am also sure that you would get more support from the community fordeploying on Apache or other open source web servers than on IIS.

Anyhow, here are more links that speak to that:http://sourceforge.net/apps/trac/pyisapiehttp://pypi.python.org/pypi/PyISAPIe/1.0.130http://stackoverflow.com/questions/704368/django-working-under-iis7http://stackoverflow.com/questions/374760/are-there-any-plans-to-officially-support-django-with-iisIs it an absolute must that you use Windows to deploy?

> Pete,>> Does this mean that we shouldn't even try to run it on IIS7 in> production?>> On Dec 1, 4:27 pm, CrabbyPete <pete.do...@gmail.com> wrote:> > I developed Djano on a windows server and everything went smoothly> > except getting it to work with IIS. I loaded apache on windows and it> > works great.> >> > On Dec 1, 6:43 am, ashdesigner <antony.shash...@gmail.com> wrote:> >> > > Hello,> >> > > I am absolutely new to Python/Django. Being responsible for a large> > > corporate startup project and having looked through a number of MVC/> > > MVT frameworks I decided to outsource the webproject in Django.> >> > > The only undiscovered issue to us is whether we can launch a heavy> > > loaded website in Django under Windows (IIS) + MSSQL. Would appreciate> > > any comment please.> >> > > Anthony>> --> 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<django-users%2bunsubscr...@googlegroups.com>> .> For more options, visit this group at>http://groups.google.com/group/django-users?hl=en.>>

Django in production on Windows

On Wed, Dec 1, 2010 at 6:43 AM, ashdesigner <antony.shash...@gmail.com> wrote:> The only undiscovered issue to us is whether we can launch a heavy> loaded website in Django under Windows (IIS) + MSSQL. Would appreciate> any comment please.

a WSGI plugin for IIS would be the best answer; but there's nothingwrong with FastCGI. properly managed can sustain as high load asanybody else.

unfortunately, the most common FastCGI->WSGI adapter (flup) is quitegood and performant; but limited in terms of dynamic process/threadlifetime managing. a more 'modern' approach could be gunicorn orTornado. since both of them handle HTTP->WSGI, your IIS frontendwould have to proxy those requests, but i guess that's a standardfeature of any webserver

Django in production on Windows

Javier,

Thanks for your reply. We will try to explore (to some extent)solutions you propose, hopefully it will help.

Anthony

On Dec 1, 6:26 pm, Javier Guerra Giraldez <jav...@guerrag.com> wrote:> On Wed, Dec 1, 2010 at 6:43 AM, ashdesigner <antony.shash...@gmail.com> wrote:> > The only undiscovered issue to us is whether we can launch a heavy> > loaded website in Django under Windows (IIS) + MSSQL. Would appreciate> > any comment please.>> a WSGI plugin for IIS would be the best answer; but there's nothing> wrong with FastCGI. properly managed can sustain as high load as> anybody else.>> unfortunately, the most common FastCGI->WSGI adapter (flup) is quite> good and performant; but limited in terms of dynamic process/thread> lifetime managing. a more 'modern' approach could be gunicorn or> Tornado. since both of them handle HTTP->WSGI, your IIS frontend> would have to proxy those requests, but i guess that's a standard> feature of any webserver>> --> Javier