There used to be a CLEAN_EXPIRED_ASSETS environment variable that allowed for cleaning expired assets at the same time as the precompile task was being executed. It was removed in 0171cf06bdd5aad1fd72ed6f44ff419bd8b42ce7 due to Heroku not supporting these environment variables. However, I would still find this very useful for our environment, so this pull request brings back that functionality.
Allowing this to execute at the same time as the precompile task can save the overhead of having to execute two separate rake tasks (and loading the whole Rails environment inside each one). We're currently looking to make the switch to JRuby for a few projects and this time savings becomes even more significant there since JRuby is slower to startup new processes.
There used to be a
CLEAN_EXPIRED_ASSETS
environment variable that allowed for cleaning expired assets at the same time as theprecompile
task was being executed. It was removed in 0171cf06bdd5aad1fd72ed6f44ff419bd8b42ce7 due to Heroku not supporting these environment variables. However, I would still find this very useful for our environment, so this pull request brings back that functionality.Allowing this to execute at the same time as the precompile task can save the overhead of having to execute two separate rake tasks (and loading the whole Rails environment inside each one). We're currently looking to make the switch to JRuby for a few projects and this time savings becomes even more significant there since JRuby is slower to startup new processes.