someone on this list, not too long ago , wanted to render their javascript/css with mako or jinja templates. so they'd be normal javascript / css files -- but in production they might have some different vars or images. an example in practice: on an earlier version of a website ( which I had inherited , not designed! ) all of the css/js were php files that were served off an Akamai CDN store. the server environment would dictate different urls for images, javascripts, css, etc -- production hit Akamai, staging/dev/local would hit a mix of staging and 'whatever the server ran on'.
i think that's similar to what you're looking at doing now ? in any event, you can easily muck around with either compiling your js/ css files or flipping around directory structures within the startup routine. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
