go all the way for iis and fastcgi. the first slice is outdated and frankly counter-productive with wfastcgi lying around.
On Monday, June 15, 2015 at 7:42:28 PM UTC+2, Leonel Câmara wrote: > > Hey, I've never tried it in production, because frankly there's just much > better choices of servers in Linux, this isn't just a web2py problem, it's > any Python framework running with WSGI. That said you should be able to get > pretty good performance by using IIS with ISAPI WSGI extension. > > Like this slice: > > http://www.web2pyslices.com/slice/show/1453/install-web2py-on-windows-with-iis > > Or even using FastCGI as explained in the book: > http://www.web2py.com/books/default/chapter/29/13/deployment-recipes#IIS > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
