I'll revise this and provide (hopefully) something automatic to let this work without too much configuration. Then we can test it and update the relevant section of the book that needs a serious update :P
On Tuesday, October 28, 2014 2:05:05 AM UTC+1, Tim Richardson wrote: > > For sure we can make better notes. But for what it's worth, these are my > notes on getting web2py working on IIS. Including Simone's solution to IIS > clobbering requests when they created or modified .py files. > > > https://docs.google.com/document/d/1uT2SS1xNMuWF38Dq2QZfe30LLnqELGeCYKgWsicz9zQ/edit?usp=sharing > > I hope this helps as an interim measure. > > By the way, apache on windows is a very stable and familiar way of hosting > web2py under windows unless the single process fr mod_wsgi becomes a > concern. Which it won't for a long time if you are careful to write good, > fast-returning code since the whole theory of nginx etc is that web servers > are very IO bound. > > However, IIS lets fastcgi access multiple cores (like Apache mod_wsgi on > linux) which was interesting to me, at least as an exercise. > -- 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.
