Sorry perhaps I don't express myself correctly, I'm not saying this is a bug or I can't do with the current way. I'm only saying that I think better if there are something like that in app level. It's an idea. Main routes.py to control things up to the application, and the rest by the application.
Main: routes.py: Domain Application --------------------------------------------------- www.domain1.com domain1 www.domain2.com domain2 Aplication: applications/domain1/routes/routes.py: In Out ---------------------------------- /favicon.ico /static/favicon.ico Final result: routes.py + application/routes. /domain1/static/favicon.ico www.domain1.com/favicon.ico In my experience in production I never share things between application or statics. I Think in the 97% or more of the application developed, to be in production are completely independant from the others app. 2011/3/24 pbreit <[email protected]> > +1 for a move towards routes default "on" and primarily controlled at the > app level. But I do recognize there is an issue about what file should come > in the main distribution and how to avoid it being overwritten with updates. > > The default files could duplicate the current default functionality for > explicitness. > -- Pablo Martín Mulone ([email protected]) http://www.tecnodoc.com.ar/ My blog: http://martin.tecnodoc.com.ar Expert4Solution Profile: http://www.experts4solutions.com/e4s/default/expert/6
