equivalent / equivalent/copy_carrierwave_file

Doesn't play nice with CarrierWave's #move_to_cache

Open
#5 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
36
Forks
18
PR merge metrics
No merged PRs in 30d

Description

CarrierWave has an option for moving files to its cache rather than copying them:

https://github.com/carrierwaveuploader/carrierwave#large-files

When using `move_to_cache`, if you're using `File.open` to open the file uploaded for the original resource, CarrierWave will move that file to its cache (and later delete it), thus destroying the original resource's file.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.