On Mon, 2008-06-16 at 13:03 +0200, Wichert Akkerman wrote: > I am trying to figure out what the best practices for dealing with > static resources such as CSS, Javascript and images are. With a > default pylons setup every request goes through two StaticURLParser > instances and files returned by them do not get any caching headers. > This is very practical for development but not ideal for a deployment > For a deployment it would be nice to be able to serve static resources > from apache or nginx. > > How do others do that? Do you use url_for to generate a URL for those > static resources and have that return a non-paster/pylons URL for > deployment environments and use the StaticURLParsers when running in > in development mode? If so, how did you set that up?
I usually just setup Nginx to handle whatever location my static content is at. It doesn't matter if Routes is setup to handle that location as the request never reaches Pylons. Cliff --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
