title: CarrierWave_Direct gem: Keep current directory structure on S3
body: <p>so I have a site already in production using the carrierwave gem with images stored on amazon s3. my uploader uses the <code>store_dir</code> method to specify a particular structure to put in processed images. </p>
  
  <p>well, now in my dev environment I've added the carrierwave_direct gem to start uploading directly to S3. The problem is this gem completely overrides the store_dir and filename defaults in my uploader. I can't push my fully working uploader live because all my old image links will be broken.</p>
  
  <p>it's my understanding that the CWdirect gem would upload a raw image file to a "temp" directory on S3, then S3 responds and gives you a <code>key</code> variable so you can grab this file and process it as you see fit. so, should i be using a completely separate image uploader class in carrierwave to process the images and place them in the correct folders? meaning I'll have one uploader dedicated to carrierwave_direct that uploads wherever this gem seems to want to upload to; and I'll use another uploader.rb class linked to my real model that keeps my current store_dir and filename structure? </p>
  
  <p>In any case, my basic question is, how can I use CarrierWave_Direct gem if I already have CW running in production with images in a specific folder structure? </p>