On Friday, October 4, 2013 9:30:17 PM UTC+2, Gour wrote: > > On Fri, 4 Oct 2013 11:53:22 -0700 (PDT) > Niphlod <nip...@gmail.com <javascript:>> wrote: > > > as often, you're making things much more complicated then they really > > are. > > I don't understand? >
if you read the code of admin, you'll quickly realize. > > My setup is nothing special, just the opposite - common scenario where > one use real webserver (nginx) on the front-end and acting as > reverse-proxy serving static content and dispatching requests for > dynamic content to the wsgi server (gunicorn) listening on > 127.0.0.1:localport. > > Actually, the setup is pretty much the same as well-known webfaction > hosting. > > this setup "binds" web2py to having knowledge ONLY of what gets passed to gunicorn. if gunicorn is listening on port 8888, then you'll need a parameters_8888.py . web2py CAN'T know in reverse-proxy environments that there is a proxy in the middle and on what port that reverse-proxy is listening. > From where do you conclude that I configured gunicorn to listen on port > 80? > > didn't you say that admin works if you place a parameters_80.py file ? then gunicorn is working on port 80, or it does simulate to work on that port. -- 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/groups/opt_out.
