uwsgi serving static content

We don't have any experience serving static content on a subpath within uwsgi, however one of the great advantages of our Control Panel is the ability to serve separate applications on a URL subpath. This is what we would recommend for a number of reasons.

First, pure static content can be served with a static-only application. This employs the webserver's front-end Nginx server to serve the pure static media (images, video, javascript, css, raw html, etc) without creating any load on your application. So, that's better than any static-media handling by web2py or uwsgi because those "mundane" static requests never have to be handled by your application at all.

Second, the control panel supports assigning URL Paths to your website record. This means it is simple and effective to employ a configuration such as:

1
2
3
4

domain.com          # URL Path of "/",        application type "Static Only (no .htaccess)".
domain.com/blog     # URL Path of "/blog",    application type "Static/CGI/PHP-5.3".
domain.com/chat     # URL Path of "/chat",    point to your uwsgi Custom Application (listening on port)
domain.com/contact  # URL Path of "/contact", point to your uwsgi Custom Application (listening on port)

In the above, the domain.com/blog is assumed to be served by a dynamic blog application (such as Wordpress) or other Static/CGI/PHP backend. If it's pure static, it can be a Static Only (no .htaccess) application type instead.

The easiest way would be to forward this traffic directly to the front-end nginx server. You can do that with a 'symbolic link to static only app' and than updating the website configuration to serve that application at the given URI. More info may be found here.