lighttpd and nginx for the webserver part, fastcgi, sgci or uwsgi for the python one.
On Wednesday, June 11, 2014 8:29:12 PM UTC+2, at wrote: > > > > On Wednesday, 11 June 2014 21:08:43 UTC+5, Niphlod wrote: >> >> this is the relevant excerpt >> >> *Note that the version of Python from which this baseline environment is >> created must be the same version of Python that mod_wsgi was compiled for. >> It is not possible to mix environments based on different major/minor >> versions of Python* >> >> Usually people need to recompile mod_wsgi manually passing the right >> python homedir. >> a good method to check in "debian-like" OS is to run >> >> ldd /usr/lib/apache2/modules/mod_wsgi.so >> >> and see what pops up >> > > Thank you Niphlod for the informative post. I'll further explore it. > > >> BTW: this is one among MAAANY reasons apache + mod_wsgi has been largely >> superseeded . Too many issues and too little flexibility in respect of >> other simpler and more performant alternatives. >> > > What are other alternatives? really interested to know about it. > Thanks > > -- 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.
