Carrierwave download file rails

Learn more. Asked 8 years, 8 months ago. Active 4 years, 8 months ago. Viewed 8k times. I'm running: Rails 3. The Whiz of Oz 6, 8 8 gold badges 46 46 silver badges 80 80 bronze badges.

Thank you so much. This all worked wonders. Rails 4 - CarrierWave. Add a comment. Active Oldest Votes. I was able to figure this out. I will attempt to explain how I fixed this problem. Thanks for this info! I am using Carrierwave gem and when i download the file, if that file name contains space then it's converted into underscores. Project Samples. Project Activity. Categories File Sharing.

License MIT License. Mit einem Experten sprechen. User Reviews Be the first to post a review of CarrierWave! Report inappropriate content. Thanks for helping keep SourceForge clean. X You seem to have CSS turned off. Briefly describe the problem required :. Upload screenshot of ad required :. If you want to upload multiple files simultaneously you'll have to use a javascript or flash uploader. Please read the CarrierWave readme first. CarrierWaveDirect works with fog so make sure you have CarrierWave set up and initialized with your fog credentials, for example:.

Check out this file for some hints on how you can customize your uploader. It should look something like this:. Remove the line storage :file and replace it with include CarrierWaveDirect::Uploader so it should look something like:.

If you're not using Rails you can generate a direct upload form to S3 similar to this example by making use of the CarrierWaveDirect helper methods. Once you've uploaded your file directly to the cloud you'll probably need a way to reference it with an ORM and process it. But if you are trying to stream video or audio you will need to set the mime type manually as Amazon will not calculate it for you.

Or you can use the helper which shows all possible content types as a select, with the default content type selected. Processing and saving file uploads are typically long running tasks and should be done in a background process. CarrierWaveDirect gives you a few methods to help you do this with your favorite background processor such as DelayedJob or Resque. The key is the most important piece of information as we can use it for validating the file extension, downloading the file from S3, processing it and re-uploading it.

See the CarrierWave readme for more info. CarrierWaveDirect automatically gives you an accessible key attribute in your mounted model when using ActiveRecord. You can use this to put a hidden field for the key into your model's form.

Now that the basic building blocks are in place you can process and save your avatar in the background. This example uses Resque but the same logic could be applied to DelayedJob or any other background processor. The method self. In Rails you could do that by adding an initializer with:. Remember, if you have already set storage :something in your uploader, the storage setting from this initializer will be ignored. If you need to test your processing, you should test it in isolation, and enable processing only for those tests that need it.

Processing can be enabled for a single version by setting the processing flag on the version like so:. If you want to use fog you must add in your CarrierWave initializer the following lines. Ensure you have it in your Gemfile:. For the sake of performance it is assumed that the directory already exists, so please create it if it needs to be. Here's a full example:. That's it! Note : for Carrierwave to work properly it needs credentials with the following permissions:. Fog is used to support Rackspace Cloud Files.

You'll need to configure a directory also known as a container , username and API key in the initializer. For the sake of performance it is assumed that the directory already exists, so please create it if need be. You can optionally include your CDN host name in the configuration. This is highly recommended, as without it every request requires a lookup of this information. Fog is used to support Google Cloud Storage.

You'll need to configure a directory also known as a bucket and the credentials in the initializer. You can still use the CarrierWave::Uploader url method to return the url to the file on Google. Since Carrierwave doesn't know which parts of Fog you intend to use, it will just load the entire library unless you use e. If you prefer to load fewer classes into your application, you need to load those parts of Fog yourself before loading CarrierWave in your Gemfile. Beware that this specific require is only needed when working with a fog provider that was not extracted to its own gem yet.

A list of the extracted providers can be found in the page of the fog organizations here. If you're uploading images, you'll probably want to manipulate them in some way, you might want to create thumbnail images for example. CarrierWave comes with a small library to make manipulating images with RMagick easier, you'll need to include it in your Uploader:.

You can set a process callback, which will call that method any time a file is uploaded. There is a demonstration of convert here. Convert will only work if the file has the same file extension, thus the use of the filename method. Check out the manipulate! This allows you to have the power of ImageMagick without having to worry about installing all the RMagick libraries.

Currently, the MiniMagick carrierwave processor provides exactly the same methods as for the RMagick processor. See the documentation for CarrierWave::Compatibility::Paperclip for more details. The Active Record validations use the Rails i18n framework.

Add these keys to your translations file:. The carrierwave-i18n library adds support for additional locales. By default, CarrierWave copies an uploaded file twice, first copying the file into the cache, then copying the file into the store. For large files, this can be prohibitively time consuming.

By default, mounting an uploader into an ActiveRecord model will add a few callbacks. For example, this code:.