A very simple and light way of deploying web2py is to use uwsgi both to handle the uwsgi communication and also act as a server.
Once one has installed uwsgi it is as simple as uwsgi --pythonpath /opt/web-apps/web2py --module wsgihandler --http : 80 -s /tmp/we2py.sock One should ensure that /tmp/ folder is writeable. Replace /opt/web- apps/web2py with the address of web2py. You can add -d /var/log/uwsgi.log as a parameter to send the logs to a file and 'daemonize' the process. The remote computer needs no other server like apache, nginx etc. It is fast and light in its use of resources and very configurable. It is maybe worth including in the book due to its simplicity. Has anyone had any experience of deploying web2py in this way? Is anyone aware of any downsides of deploying in this way? Does anyone know how it would compare with the rocket server? Peter
