fcheung / asset_symlink Goto Github PK

the current rubygems.org version is 0.1 and doesn't support rails4

For symlinked assets the cache control header is:

cache-control: public, max-age=14400

This is the same header used for the non-symlinked asset.

I'm sure this is the intended behavior, but I can imagine that for some use cases you would want the symlinked assed to have a shorter cache expiration so that if the source JS file is changed, clients will download the new code.

Following the example in the README, if you distribute a "widget.js" asset to clients, and then push a bugfix to widget.js, CDNs & browser that already have the old asset cached will not download the code that has the bugfix.

Is there any known way around this? I can't seem to find a way to change the cache-control header for only "symlinked assets".

Hello there @fcheung

I have been running this gem in Rails 6.0.0 without any problems for quite some time but today I found that when updating to Rails 6.0.2.1, asset_symlink seems to lock the dependency to Rails 5 (6.0.0?)

Could you expand the support to Rails 6.* ?

Thanks for this gem by the way! It solves a painful issue with the asset pipeline

Hi there,
Is there any chance that version for Rails 5 will be released?
Thanks in advance