Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[close #797] Do not carry asset pipeline fragment cache into runtime #812

Merged
merged 4 commits into from
Oct 30, 2018

Conversation

schneems
Copy link
Contributor

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 schneems force-pushed the schneems/no-assets-cache-at-runtime branch from a168296 to 9fc1cd3 Compare September 17, 2018 15:30
@schneems schneems force-pushed the schneems/no-assets-cache-at-runtime branch 2 times, most recently from 2087ced to 1d70e6e Compare October 15, 2018 22:34
@schneems schneems force-pushed the schneems/no-assets-cache-at-runtime branch from 1d70e6e to b78d39a Compare October 17, 2018 19:12
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 schneems force-pushed the schneems/no-assets-cache-at-runtime branch from b78d39a to 7303f8f Compare October 23, 2018 16:26
@schneems schneems merged commit 424a724 into master Oct 30, 2018
@edmorley edmorley deleted the schneems/no-assets-cache-at-runtime branch August 27, 2020 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants