[web2py] Re: using anyserver.py in production

2015-06-09 Thread Lewis
Someday, I'll try ansible. Spelling correction to the rescue. On Sunday, June 7, 2015 at 7:51:06 PM UTC-7, Lewis wrote: > > Thanks for all this. > > So, the world seems to back UWSGI as the preferrred solution. I'll get > over it. I see that you are saying that once when one does need > perfo

[web2py] Re: using anyserver.py in production

2015-06-07 Thread Lewis
Thanks for all this. So, the world seems to back UWSGI as the preferrred solution. I'll get over it. I see that you are saying that once when one does need performance tuning with multiple workers, uwsgi is both more performant and more tunable. I think having a fabric deploy script will sol

[web2py] Re: using anyserver.py in production

2015-06-04 Thread Niphlod
On Thursday, June 4, 2015 at 5:57:36 PM UTC+2, Lewis wrote: > > What about gunicorn as a wsgi server to simply stand between nginx and > web2py? > gunicorn behind nginx is a popular config, but usually is to have several gevented processes to bind on a single socket. There are several "workers

[web2py] Re: using anyserver.py in production

2015-06-04 Thread Lewis
What about gunicorn as a wsgi server to simply stand between nginx and web2py? Here is what I am going to do: 1. script (Bash) my config so that it is repeatable. This will be similar to the existing scripts supplied with web2py, but with small changes. test it in a new deployment on a clean

[web2py] Re: using anyserver.py in production

2015-06-04 Thread Niphlod
cherrypy or rocket may sustain an average of 50 concurrent users (again, on an average linode server, etc etc etc). no multiprocess usage. no defense against common attacks like slowloris. I'm not advocating at all twisted, tornado or gevent 'cause your app needs to be rewritten to use what th

[web2py] Re: using anyserver.py in production

2015-06-03 Thread Lewis
Those 19 lines had been in place from before 2013 (probably 2011!), which is why I missed the change. That site is not really "production" except for the fact that it faces the public internet. Probably has no visitors except me; I just want to learn how to configure and manage something tha

[web2py] Re: using anyserver.py in production

2015-06-03 Thread Niphlod
anyone is free to do whatever he/she wants. Few things to consider: uwsgi is by far the most complete piece of production-ready "thingy" to run your app into. Given that a frontend IMHO is required, when you set a reverse proxy to anyserver.py (vs setting uwsgi) if you don't have specific requi

[web2py] Re: using anyserver.py in production

2015-06-03 Thread Lewis
I should point out this minimal approach doesn't support https, so the admin console can't be reached. Login also can't be used without https and ssl. The digital ocean article shows how to enable ssl for cherrypy. Hopefully, I can interpolate a bit and actually use nginx to do the https rou

[web2py] Re: using anyserver.py in production

2015-06-03 Thread Lewis
This worked: python anyserver.py -s cherrypy -i 0.0.0.0 -p 80 > logfile & I get the reverse proxy thing. Currently, I have uwsgi behind nginx which works. However, uwsgi's settings are twiddly; seem to change between versions; the documentation, while extensive, is challenging; and I don't n

[web2py] Re: using anyserver.py in production

2015-06-02 Thread Niphlod
use -i 0.0.0.0 to listen on all available interfaces. BTW#1: the default webserver (rocket) and cherrypy (what you seem to want using) have nearly the same performances BTW#2: unless you have some specific requirements, for an internet-facing server is ALWAYS recommended to use a real webserve