On 15 December 2015 at 08:12, Frederick Cheung <[email protected]> wrote: > On Tuesday, December 15, 2015 at 6:57:36 AM UTC, Fernando Cordeiro wrote: > >> >> The Asset Pipeline is amazing and I'm all for opinionated solutions, but I'm >> all for solutions, and the decision to not use querystrings, albeit >> respectable in the sense it leverages proxies, creates a problem where mails >> sent today may appear without a logo in the near future. >> >> I am not saying this should change (unless all or at least most caching >> proxies started picking up query strings, if that's the case maybe changing >> is a good idea). I'm just looking for a solution to serve (At least some of) >> the assets that were deleted by using the newest version, even with >> different digests. I had to upload files to the public folder more than a >> few times, and I feel like it's an awful way to fix it. >> > > The standard way to solve this (if serving the assets directly) is to symlink > public/assets to a folder that persists across deploys - this way old assets > remain available. If you use Capistrano to deploy your apps this is done with > you (and they also provide a rake task for deleting assets that haven't been > deployed in over a certain (configurable) time.
An even better solution to your problem with emails is not to embed linked images in emails. Many, many people have image download disabled in their email viewer (possibly gmail defaults to this mode, not sure). Also the images are not available when viewing email offline. Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLtsRqY1q4s9%3DGO-QMnost57ijD_1gQihJpmK5%2B9pdNXrQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
