Do not carry asset fragment cache into runtime #797
Comments
schneems
added a commit
that referenced
this issue
Sep 17, 2018
When someone is using the asset pipeline, and they've disabled the config that allows them to build assets in production. So when ``` config.assets.compile = false ``` Then the `tmp/cache/assets/sprockets/` folder is not needed at runtime and should be safe to delete, which will lower the overall slug size. Do not merge until after Dreamforce.
schneems
added a commit
that referenced
this issue
Oct 15, 2018
When someone is using the asset pipeline, and they've disabled the config that allows them to build assets in production. So when ``` config.assets.compile = false ``` Then the `tmp/cache/assets/sprockets/` folder is not needed at runtime and should be safe to delete, which will lower the overall slug size. Do not merge until after Dreamforce.
schneems
added a commit
that referenced
this issue
Oct 30, 2018
[close #797] Do not carry asset pipeline fragment cache into runtime
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When someone is using the asset pipeline, and they've disabled the config that allows them to build assets in production.
So when
Then the
tmp/cache/assets/sprockets/folder is not needed at runtime and should be safe to delete, which will lower the overall slug size.The text was updated successfully, but these errors were encountered: