-
Notifications
You must be signed in to change notification settings - Fork 87
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
Non-digest only mode (move instead of copy) #44
Comments
I'm just a non-stupid-digest-assets user, but I imagine moving the digested assets completely would break most applications. Perhaps adding a mode for copy, move, or symlink would be useful? I forget the disadvantages of symlink over copy in this situation but if I recall there are some other than the obvious bonus of not duplicating files. |
@courtland the proposed change would definitely keep the status quo by default (see my note about the default being Here's what I'm proposing master...abrom:master along with
will move instead of copy. |
A PR for this sounds good to me, I wouldn't use it personally but I can see it might be useful |
I think you can just set |
For various reasons we've gone for a setup where cache busting is provided at a higher level (root of the path) so digesting of any sort isn't useful (actually just gets in the way). Using this gem solves the problem but leaves our asset bundle double the size it really needs to be.
I'm going to patch a fork to include a
non_digest_asset_mode
or similar setting. Default beingcopy
but optionallymove
.Would this be something you'd be interested in?
The text was updated successfully, but these errors were encountered: