As someone mentioned in the comments, appending a hash to the asset paths is a default part of the asset pipeline.
In production, Rails inserts an MD5 fingerprint into each filename so that the file is cached by the web browser
You can read more about fingerprinting in the asset pipeline here. Rails uses Sprockets to compile assets. The fingerprinting comes as part of Sprockets process.
You can use Sprockets' find_asset
method, passing in a logical path to your asset to get a Sprockets::BundledAsset
instance. For example
[1] pry(main)> Rails.application.assets.find_asset('application.js')
=> #<Sprockets::BundledAsset:0x3fe368ab8070 pathname="/Users/deefour/Sites/MyApp/app/assets/javascripts/application.js", mtime=2013-02-03 15:33:57 -0500, digest="ab07585c8c7b5329878b1c51ed68831e">
You can call digest_path
on this object to get it's MD5
sum appended to the asset.
[1] pry(main)> Rails.application.assets.find_asset('application.js').digest_path
=> "application-ab07585c8c7b5329878b1c51ed68831e.js"
With this knowledge you can easily create a helper to return the digest_path
for any asset in your application, and call this helper from within your .js.erb
files.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…