Web apps with hashes in asset filenames have this problem: 1. A deploy starts. 2. A browser starts loading a page. 3. The deploy finishes. 4. The browser requests assets referenced by the page. 5. Those assets no longer exist due to the deploy.
-
Show this thread
-
What's the standard solution to this? We're on Heroku, so the old asset files aren't available after a fresh deploy. I can write a server-side route that detects requests for old assets and... I'm not even sure what it should do. But presumably there's a standard solution?
7 replies 0 retweets 20 likesShow this thread -
Replying to @garybernhardt
Serve your assets from a CDN backed by something like S3
1 reply 0 retweets 1 like
Replying to @sgrif @garybernhardt
(Sorry I should have realized all your replies are exactly this advice already)
2:17 PM - 15 Mar 2020
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.