On Saturday, February 10, 2018 at 8:29:00 PM UTC-8, lucas wrote:
> better use nginx to serve web2py, found a lot of problem when using apache 
> with web2py
> is it really much much better?  in what ways?  why would I change?  Lucas

First off, Massimo and the other leads  recommend it ("apache has too much 

And then, regarding Alex's comment, it's easy enough to set up that I 
managed it.

My initial config file was similar to the one in the box, but I first made 
sure that I knew what the pieces of the template were doing.  Just 
yesterday, I added rate limiting on a particular URL, as well as 
determining how to block IPs.

The Nginx site has pretty good documentation:


and there's some useful 3rd party documentation:
I got *9781785289538-NGINX_ESSENTIALS.pdf* and 
*9781782165125-INSTANT_NGINX_STARTER.pdf* from there.


- 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.

Reply via email to