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

Keep default Carrierwave paths? #98

Closed
octimizer opened this issue Aug 20, 2013 · 2 comments
Closed

Keep default Carrierwave paths? #98

octimizer opened this issue Aug 20, 2013 · 2 comments

Comments

@octimizer
Copy link

Hi,

is there a way to use CarrierWaveDirect but keep the default store_dir filenames and paths from CarrierWave?

Or how would you go about switching an existing Carrierwave project to CarrierWaveDirect without breaking paths and filenames and without having to regenerate versions ? (video attachments can be a pain to regenerate.)

@shlomizadok
Copy link

@p8 p8 closed this as completed Mar 9, 2015
@hankish
Copy link

hankish commented Aug 8, 2015

Btw... The technique linked to above still felt a little hacky to me. This is another technique to consider: http://stackoverflow.com/questions/14791655/carrierwave-direct-gem-keep-current-directory-structure-on-s3

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

No branches or pull requests

4 participants