On Jun 21, 10:44 pm, Giuseppe Luca Scrofani <glsdes...@gmail.com> wrote: > But now my question is, I read in > manual the included wsgi server in web2py it is not intended for > production use due to lack of configurability. But this for a small > site make sense?
It depends :) I run an intranet app serving some tens of users with the stock web2py as-is, with no problems whatsoever. In fact, in this scenario, it would be worse to run something like Apache & PG, because that would be time-consuming overkill with no benefit whatsoever. However, I would probably not run CherryPy on the general internet, or anywhere where I might expect to begin getting thousands of requests per day. I don't know the security issues of CherryPy at all, but I do know that servers like Apache and Lighttpd are much more battle-hardened, and so that would inform my choice in those situations. Personally, I think stock web2py in an intranet-like use-case is a compelling proposition in general, but sqlite can become a bottleneck pretty quickly as concurrent use grows. I suspect that will be a performance bottleneck before the web server. Also, I think newer web2py builds use Rocket instead of CherryPy, but I really don't know much more about the details to help further.
