Databases
StackOverflow2013
Postsdbo
POCloudfront loading old (css/js) files after rails deployment with capistrano
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCloudfront loading old (css/js) files after rails deployment with capistrano
    primarykey
    data
    text
    <p>I'm using Amazon's Cloudfront CDN along with Rails for our app and I'm now encountering a strange issue that I can't track down.</p> <p>We store css and js files in Cloudfront and use the RELEASE value from capistrano in order to 'version' the files. (Method used here: <a href="http://stdout.wooswiff.com/2011/01/no-fuss-amazon-cloudfront-cdn-for-your.html" rel="nofollow">http://stdout.wooswiff.com/2011/01/no-fuss-amazon-cloudfront-cdn-for-your.html</a> )</p> <p>A typical path to a file is: <a href="http://assets1.ourhost.com/rel-20120117173438/assets/main.css" rel="nofollow">http://assets1.ourhost.com/rel-20120117173438/assets/main.css</a></p> <p>The '20120117173438' is our RELEASE value that Capistrano creates during the deployment.</p> <p>On deploy that RELEASE value is changed and then Cloudfront comes back to our app servers to get the new file. I've got some rewrite stuff going on server-side to ignore the RELEASE value in the path and serve up the currently existing file from the filesystem.</p> <p>The issue is this: on every deploy those RELEASE values are being updated correctly, so the sources being used to fetch the css and js files <em>is</em> being updated correctly, however, Cloudfront is serving us an older version of the file, from the previous deploy.</p> <p>The only way for the correct files to be sourced is for me to do a second deploy in order to change the RELEASE value yet again.</p> <p>The browser is not cacheing the files, so it's something going on with Cloudfront.</p> <p>Has anyone seen anything similar to this? I'd love some extra input on what to look for.</p> <p>Thanks.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USnduro
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI *think* I have narrowed down the problem and it is related to the deploy process itself. We have multiple app servers and we pull them out from the load balancer, one at a time, during deploys. I believe what is happening is that as an updated machine goes back live, a client hits it which results in a call to Cloudfront using the new release path. Cloudfront goes back to the origin server but gets one that is not yet updated and that is polluting the cache in Cloudfront. It seems I'm going to need to alter the deploys.
      singulars
      1. POCloudfront loading old (css/js) files after rails deployment with capistrano
      1. USnduro
    2. COHave you looked at the asset pipeline? By having versions that are tied to the content you're guaranteed not to have that cache pollution problem
      singulars
      1. POCloudfront loading old (css/js) files after rails deployment with capistrano
      1. USFrederick Cheung
    3. COWe are on Rails 3.0 so the asset pipeline is not quite what it is in 3.1 and above. Is there something specific to 3.0 that might be useful in this situation? Thanks.
      singulars
      1. POCloudfront loading old (css/js) files after rails deployment with capistrano
      1. USnduro
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload