the beauty of R&D + trial and errors always amazes me. Many thanks you for keep trying and opening my eyes to what I sincerely didn't test in the latest revision of wfastcgi.py . I'm going to test it further and figure out the best logic to handle web2py in iis and - possibly - provide a setup script that ties all things up in a tidy way. Maybe later we can ship it into scripts/* with a proper web.config in examples/*.
To be exact, I found out that wfastcgi.py handles its own watcher thread over modified files that by default are any .config (usually used to configure IIS apps) AND *.py files. while this can be a sound default for "pull" frameworks like django or flask, it dies abruptely with "push" ones like web2py that create *.py files themselves. The url-rewrite module is needed just to handle static_version and having iis serving static files instead of letting fastcgi handle them. On Saturday, October 25, 2014 8:38:40 AM UTC+2, Tim Richardson wrote: > > Ok, Simone is a legend. He found that a recent change in Microsoft's > wfastcgi.py was causing the problem. He suggested a fix requiring IIS's URL > rewrite module, which I have tested and it works. I've moved from apache to > IIS now and I'll see how it goes over the coming week. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
