Asset pipeline docs refer to no-longer-working config.assets.cache_store

[jonswar]

config.assets.cache_store no longer seems to do anything. In my own console:

irb(main):004:0> Rails.application.config.assets.cache_store
=> :memory_store
irb(main):005:0> Rails.application.assets.cache.class
=> Sprockets::Cache::FileStore

and elsewhere on the web:

#10334
http://damon.theidealweb.com/config-assets-cache_store-and-rails-4/

But it is still mentioned as the default way to configure the cache in http://guides.rubyonrails.org/asset_pipeline.html#assets-cache-store

[rafaelfranca]

cc @zzak

[zzak]

nfi bro /cc @rafaelfranca @arthurnn

[rafaelfranca]

Hahaha, you were investigating sprockets related documentation so I thought
you already knew this. I know what needs to be done but I'm almost sure we
will have to rewrite all this guide now with sprockets 3. I'll do that if
you are fine, since I have more background on the matter.

On Wed, Apr 22, 2015, 02:31 Zachary Scott notifications@github.com wrote:

nfi bro /cc @rafaelfranca https://github.com/rafaelfranca @arthurnn
https://github.com/arthurnn

—
Reply to this email directly or view it on GitHub
#19835 (comment).

[zzak]

@rafaelfranca Let's collaborate on a new guide for sprockets! <3

[davidbalbert]

@zachallaun and I were working on a related bug and did some poking around before we ran into this issue. I believe this came from a change to sprockets-rails and isn't related to Sprockets 3: We've confirmed that config.assets.cache_store has no effect with sprockets 2.12.4 and sprockets-rails 2.3.2 (the latest sprockets-rails as of this writing). The sprocket-rails README also contains an example of using config.assets.configure to set the cache.

The relevant commit (from 2012) is rails/sprockets-rails@ecaeb27. The commit message refers to rails/sprockets-rails#3, which is an unrelated issue. Given that the repo was moved at some point, my guess is it's probably referring to issue 3 on sstephenson/sprockets-rails, but the issue tracker for that repo has been disabled.

@sstephenson, is there any chance the contents of that issue is still available somewhere? It would be helpful for the related bug that we're looking into. I don't know what happens to an issue when the GitHub issue tracker gets disabled.

[rails-bot]

This issue has been automatically marked as stale because it has not been commented on for at least
three months.

The resources of the Rails team are limited, and so we are asking for your help.

If you can still reproduce this error on the 4-2-stable, 4-1-stable branches or on master,
please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions.