On Saturday, January 7, 2012 8:28:46 AM UTC-8, Craig Younkins wrote: > > For our site we actually have a build process for our CSS templates at > application start. This way we can have different domains depending on the > configuration (testing, prod, dev), and it all works with the same > templates. They are compiled at application start rather than being served > dynamically because the context never changes and we can take advantage of > nginx's speed at serving static content. >
At work, I deploy several Pylons and Pyramid apps to various environments with different host names and application prefixes, and it seems to me that a build step such as this shouldn't be necessary. A combination of relative paths in CSS and appropriate static file configuration does the trick. I'm curious why this wouldn't work for your app. Can you share your code? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/M9ZmPVP3_m0J. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
