Op 11 nov. 2014 18:45 schreef "John Anderson" <[email protected]>: >> > I still don't think just putting it behind a CDN as a cache quite solves the asset deployment issue. Using the same domain as your application is going to pass around all the cookies for that domain on every static asset request. You have to be able to customize the root URL of static assets when it generates the URL in production. This is why you see things like twimg.com and yimg.com, or just applications using akamai URLs directly. It doesn't make much sense to use up application server workers (like gunicorn) to serve a CSS file, especially if you aren't using gevent because then you are going to have a static set of threads + processes that you've configured, especially since you rarely expose it directly and are usually sitting behind a proxy like nginx anyways. >
In my situation the CDN is behind a different domain name as the main site: cdn.example.com vs www.example.com. In bowerstatic you can define that the statics assets will have a different base than the regular pages. Therefor cdn.example.com has no cookies. For me this is a nice solution, but will not be others. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
