markrcote/templeton — Issue #15: Allow specification of path for dynamic and static content
Author: markrcote
Created: 2011-12-23 04:48:48+00:00
State: open

Templeton more-or-less enforces a path structure, placing static content at the root and dynamic content under api/. Technically you can override the location of dynamic content in handlers.py, but the app server will still put it under api/ in the nginx config file. We can potentially have some way for the app server to identify when an app wants to serve its dynamic content under a different path--and may as well do this for static content too.