We strongly recommend nginx for most users. Rocket (built-in), Tornado, and Unicorn all work great too but they do not have as many customizations as nginx.
On Sunday, 9 August 2015 01:34:46 UTC-5, Rafal Dobosz wrote: > > What are some servers you do recommend? > > On Tuesday, 4 August 2015 11:17:37 UTC-4, Massimo Di Pierro wrote: >> >> Yes. It should. I agree. We should leave the sections on Apache but >> comment they we do not recommend apache. >> >> On Monday, 3 August 2015 10:23:58 UTC-5, Niphlod wrote: >>> >>> IMHO given that the majority of issues reported come with "one step >>> production deployment" keywords, the book chapter >>> http://web2py.com/books/default/chapter/29/13/deployment-recipes#One-step-production-deployment >>> >>> should be redacted to point to the script provisioning uwsgi and nginx >>> instead of the bugged one provisioning apache. >>> >>> On Friday, July 31, 2015 at 7:19:54 PM UTC+2, Massimo Di Pierro wrote: >>>> >>>> I think that commit should be reversed. O changed to processes=5 >>>> threads=1. but this may cause an increased memory usage and it is not a >>>> good thing with apache. Agreed that Apache is no longer recommended (not >>>> just for web2py users) but we should continue to support it because it is >>>> still the mots popular web server. >>>> >>>>> >>>>>>>> -- 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/d/optout.
