How to reset Heroku Rails4 asset pipeline cache

Question

According to Heroku documentation:

Heroku now caches 50mb worth of tmp/cache/assets which is a cache directory for the asset pipeline to store intermediate files. This means that future asset compilations will be faster due to not having to recalculate these files.

My question is how do I manually reset or delete this cache so that all of my assets have to be precompiled again? I tried heroku run console and Rails.cache.clear but it did not work. The reason I want to reset the cache is I have changed the config.action_controller.asset_host in my production.rb file but Heroku is not picking up on the change because of the cache.

score 16 · Answer 1 · answered Mar 27 '15 at 16:56

16

To purge Heroku's asset cache, you need the Heroku Repo plugin to the Heroku toolbelt. Install that, then use the command

heroku repo:purge_cache

Deploy after purging the cache.

answered Mar 27 '15 at 16:56

dodgio

2,169
21
19

1

This takes a minute or two to try out and probably does everything the other answers do and more. Fixed everything for me after trying other solutions forever, thank you – Tom Prats Oct 16 '15 at 06:12
'heroku run rake assets:clobber ...' did NOT work for me. This did. The "takes a minute or two" is key. – traday Jan 21 '16 at 23:18
I was getting 'remote: LoadError: cannot load such file -- coffee_script' errors during a heroku push/precompile because some coffee file was cached somewhere on heroku. This is the only cache purge that worked to clear that up. (ie assets:clobber didnt fix it) – Michael May 12 '17 at 15:02

score 13 · Accepted Answer · edited May 12 '17 at 19:34

13

Hopefully this helps. To get changes to Heroku in development I run rake assets:clean and then rake assets:precompile RAILS_ENV=production --trace before committing and pushing to Heroku

edited May 12 '17 at 19:34

Kick Buttowski

6,709
13
37
58

answered Apr 09 '14 at 23:10

user1854802

388
3
14

5

This worked thanks. Instead of running `rake assets:clean` I ran `rake assets:clobber` as I read that `rake assets:clean` has been replaced with `rake assets:clobber` for Rail 4 http://stackoverflow.com/a/15355381/1276696 – diasks2 Apr 09 '14 at 23:50
1

...the key being "before committing and pushing to Heroku". Don't run "rake assets:precompile on Heroku, it won't do anything. – Kees Briggs Mar 06 '17 at 03:21

score 4 · Answer 3 · answered Apr 09 '14 at 23:23

4

For cleaning assets, run:

rake assets:clobber

answered Apr 09 '14 at 23:23

Absurdim

233
3
15

Thanks. I tried that but it didn't work. It took 6 seconds to precompile on a push before I did the clobber and still 6 seconds after and my files still hadn't changed. – diasks2 Apr 09 '14 at 23:37

jstnno · Answer 4 · 2017-08-13T07:33:33.717

1

I had this problem, then i realized I forgot to configure to serve static assets on the production env, inside config/enviroments/production.rb

config. serve_static_files = true

edited Aug 13 '17 at 07:33

answered May 08 '15 at 05:14

jstnno

1,035
1
11
13

1

**serve_static_assets** is **deprecated** in Rails 4.2. It changed to **config.serve_static_files** – Kick Buttowski Aug 13 '17 at 04:29

Isaac Betesh · Answer 5 · 2021-02-25T00:07:18.087

1

As this Stack Overflow answer explains, config.assets.version exists for this purpose.

Most likely, you'll find it in config/application.rb or config/initializers/assets.rb. Change it to any value you want to break the cache next time you deploy to any environment.

edited Feb 25 '21 at 00:07

answered Feb 24 '21 at 22:28

Isaac Betesh

2,935
28
37

How to reset Heroku Rails4 asset pipeline cache

5 Answers5

Linked