Are you happy with your logging solution? Would you help us out by taking a 30-second survey? Click here


Classier solution for file uploads for Rails, Sinatra and other Ruby web frameworks

Star full 4f7b624809470f25b6493d5a7b30d9b9cb905931146e785d67c86ef0c205a402Star full 4f7b624809470f25b6493d5a7b30d9b9cb905931146e785d67c86ef0c205a402Star full 4f7b624809470f25b6493d5a7b30d9b9cb905931146e785d67c86ef0c205a402Star full 4f7b624809470f25b6493d5a7b30d9b9cb905931146e785d67c86ef0c205a402Star half bd79095782ee4930099175e5ce7f4c89fa3ddabcd56fffcc7c74f6f2a2d46b27 (1 ratings)
Rated 4.5 out of 5
Subscribe to updates I use carrierwave

Statistics on carrierwave

Number of watchers on Github 7884
Number of open issues 217
Average time to close an issue 13 days
Main language Ruby
Average time to merge a PR 10 days
Open pull requests 56+
Closed pull requests 32+
Last commit over 1 year ago
Repo Created about 11 years ago
Repo Last Updated over 1 year ago
Size 3.2 MB
Organization / Authorcarrierwaveuploader
Latest Releasev0.10.0
Page Updated
Do you use carrierwave? Leave a review!
View open issues (217)
View carrierwave activity
View on github
Fresh, new opensource launches 🚀🚀🚀
Trendy new open source projects in your inbox! View examples

Subscribe to our mailing list

Evaluating carrierwave for your project? Score Explanation
Commits Score (?)
Issues & PR Score (?)
What people are saying about carrierwave Leave a review


This gem provides a simple and extremely flexible way to upload files from Ruby applications. It works well with Rack based web applications, such as Ruby on Rails.

Build Status Code Climate


Getting Help

  • Please ask the community on Stack Overflow for help if you have any questions. Please do not post usage questions on the issue tracker.
  • Please report bugs on the issue tracker but read the getting help section in the wiki first.


Install the latest release:

$ gem install carrierwave

In Rails, add it to your Gemfile:

gem 'carrierwave', '~> 1.0'

Finally, restart the server to apply the changes.

As of version 1.0, CarrierWave requires Rails 4.0 or higher and Ruby 2.0 or higher. If you're on Rails 3, you should use v0.11.0.

Getting Started

Start off by generating an uploader:

rails generate uploader Avatar

this should give you a file in:


Check out this file for some hints on how you can customize your uploader. It should look something like this:

class AvatarUploader < CarrierWave::Uploader::Base
  storage :file

You can use your uploader class to store and retrieve files like this:

uploader =!(my_file)


CarrierWave gives you a store for permanent storage, and a cache for temporary storage. You can use different stores, including filesystem and cloud storage.

Most of the time you are going to want to use CarrierWave together with an ORM. It is quite simple to mount uploaders on columns in your model, so you can simply assign files and get going:


Make sure you are loading CarrierWave after loading your ORM, otherwise you'll need to require the relevant extension manually, e.g.:

require 'carrierwave/orm/activerecord'

Add a string column to the model you want to mount the uploader by creating a migration:

rails g migration add_avatar_to_users avatar:string
rake db:migrate

Open your model file and mount the uploader:

class User < ActiveRecord::Base
  mount_uploader :avatar, AvatarUploader

Now you can cache files by assigning them to the attribute, they will automatically be stored when the record is saved.

u =
u.avatar = params[:file] # Assign a file like this, or

# like this'somewhere') do |f|
  u.avatar = f
u.avatar.url # => '/url/to/file.png'
u.avatar.current_path # => 'path/to/file.png'
u.avatar_identifier # => 'file.png'

Note: u.avatar will never return nil, even if there is no photo associated to it. To check if a photo was saved to the model, use u.avatar.file.nil? instead.

DataMapper, Mongoid, Sequel

Other ORM support has been extracted into separate gems:

There are more extensions listed in the wiki

Multiple file uploads

CarrierWave also has convenient support for multiple file upload fields.


Add a column which can store an array. This could be an array column or a JSON column for example. Your choice depends on what your database supports. For example, create a migration like this:

For databases with ActiveRecord json data type support (e.g. PostgreSQL, MySQL)

rails g migration add_avatars_to_users avatars:json
rake db:migrate

For database without ActiveRecord json data type support (e.g. SQLite)

rails g migration add_avatars_to_users avatars:string
rake db:migrate

Note: JSON datatype doesn't exists in SQLite adapter, that's why you can use a string datatype which will be serialized in model.

Open your model file and mount the uploader:

class User < ActiveRecord::Base
  mount_uploaders :avatars, AvatarUploader
  serialize :avatars, JSON # If you use SQLite, add this line.

Make sure your file input fields are set up as multiple file fields. For example in Rails you'll want to do something like this:

<%= form.file_field :avatars, multiple: true %>

Also, make sure your upload controller permits the multiple file upload attribute, pointing to an empty array in a hash. For example:

params.require(:user).permit(:email, :first_name, :last_name, {avatars: []})

Now you can select multiple files in the upload dialog (e.g. SHIFT+SELECT), and they will automatically be stored when the record is saved.

u =[:user])!
u.avatars[0].url # => '/url/to/file.png'
u.avatars[0].current_path # => 'path/to/file.png'
u.avatars[0].identifier # => 'file.png'

Changing the storage directory

In order to change where uploaded files are put, just override the store_dir method:

class MyUploader < CarrierWave::Uploader::Base
  def store_dir

This works for the file storage as well as Amazon S3 and Rackspace Cloud Files. Define store_dir as nil if you'd like to store files at the root level.

If you store files outside the project root folder, you may want to define cache_dir in the same way:

class MyUploader < CarrierWave::Uploader::Base
  def cache_dir

Securing uploads

Certain files might be dangerous if uploaded to the wrong location, such as PHP files or other script files. CarrierWave allows you to specify a whitelist of allowed extensions or content types.

If you're mounting the uploader, uploading a file with the wrong extension will make the record invalid instead. Otherwise, an error is raised.

class MyUploader < CarrierWave::Uploader::Base
  def extension_whitelist
    %w(jpg jpeg gif png)

The same thing could be done using content types. Let's say we need an uploader that accepts only images. This can be done like this

class MyUploader < CarrierWave::Uploader::Base
  def content_type_whitelist

You can use a blacklist to reject content types. Let's say we need an uploader that reject JSON files. This can be done like this

class NoJsonUploader < CarrierWave::Uploader::Base
  def content_type_blacklist
    ['application/text', 'application/json']

Filenames and unicode chars

Another security issue you should care for is the file names (see Ruby On Rails Security Guide). By default, CarrierWave provides only English letters, arabic numerals and some symbols as white-listed characters in the file name. If you want to support local scripts (Cyrillic letters, letters with diacritics and so on), you have to override sanitize_regexp method. It should return regular expression which would match all non-allowed symbols.

CarrierWave::SanitizedFile.sanitize_regexp = /[^[:word:]\.\-\+]/

Also make sure that allowing non-latin characters won't cause a compatibility issue with a third-party plugins or client-side software.

Setting the content type

As of v0.11.0, the mime-types gem is a runtime dependency and the content type is set automatically. You no longer need to do this manually.

Adding versions

Often you'll want to add different versions of the same file. The classic example is image thumbnails. There is built in support for this*:

Note: You must have Imagemagick and MiniMagick installed to do image resizing. MiniMagick is a Ruby interface for Imagemagick which is a C program. This is why MiniMagick fails on 'bundle install' without Imagemagick installed.

Some documentation refers to RMagick instead of MiniMagick but MiniMagick is recommended.

To install Imagemagick on OSX with homebrew type the following:

$ brew install imagemagick
class MyUploader < CarrierWave::Uploader::Base
  include CarrierWave::MiniMagick

  process resize_to_fit: [800, 800]

  version :thumb do
    process resize_to_fill: [200,200]


When this uploader is used, an uploaded image would be scaled to be no larger than 800 by 800 pixels. The original aspect ratio will be kept. A version called thumb is then created, which is scaled to exactly 200 by 200 pixels.

If you would like to crop images to a specific height and width you can use the alternative option of '''resize_to_fill'''. It will make sure that the width and height specified are filled, only cropping if the aspect ratio requires it.

The uploader could be used like this:

uploader =!(my_file)                              # size: 1024x768

uploader.url # => '/url/to/my_file.png'               # size: 800x800
uploader.thumb.url # => '/url/to/thumb_my_file.png'   # size: 200x200

One important thing to remember is that process is called before versions are created. This can cut down on processing cost.

It is possible to nest versions within versions:

class MyUploader < CarrierWave::Uploader::Base

  version :animal do
    version :human
    version :monkey
    version :llama

Conditional versions

Occasionally you want to restrict the creation of versions on certain properties within the model or based on the picture itself.

class MyUploader < CarrierWave::Uploader::Base

  version :human, if: :is_human?
  version :monkey, if: :is_monkey?
  version :banner, if: :is_landscape?


  def is_human? picture

  def is_monkey? picture
    model.favorite_food == 'banana'

  def is_landscape? picture
    image =
    image[:width] > image[:height]


The model variable points to the instance object the uploader is attached to.

Create versions from existing versions

For performance reasons, it is often useful to create versions from existing ones instead of using the original file. If your uploader generates several versions where the next is smaller than the last, it will take less time to generate from a smaller, already processed image.

class MyUploader < CarrierWave::Uploader::Base

  version :thumb do
    process resize_to_fill: [280, 280]

  version :small_thumb, from_version: :thumb do
    process resize_to_fill: [20, 20]


The option :from_version uses the file cached in the :thumb version instead of the original version, potentially resulting in faster processing.

Making uploads work across form redisplays

Often you'll notice that uploaded files disappear when a validation fails. CarrierWave has a feature that makes it easy to remember the uploaded file even in that case. Suppose your user model has an uploader mounted on avatar file, just add a hidden field called avatar_cache (don't forget to add it to the attr_accessible list as necessary). In Rails, this would look like this:

<%= form_for @user, html: { multipart: true } do |f| %>
    <label>My Avatar</label>
    <%= f.file_field :avatar %>
    <%= f.hidden_field :avatar_cache %>
<% end %>

It might be a good idea to show the user that a file has been uploaded, in the case of images, a small thumbnail would be a good indicator:

<%= form_for @user, html: { multipart: true } do |f| %>
    <label>My Avatar</label>
    <%= image_tag(@user.avatar_url) if @user.avatar? %>
    <%= f.file_field :avatar %>
    <%= f.hidden_field :avatar_cache %>
<% end %>

Removing uploaded files

If you want to remove a previously uploaded file on a mounted uploader, you can easily add a checkbox to the form which will remove the file when checked.

<%= form_for @user, html: { multipart: true } do |f| %>
    <label>My Avatar</label>
    <%= image_tag(@user.avatar_url) if @user.avatar? %>
    <%= f.file_field :avatar %>

      <%= f.check_box :remove_avatar %>
      Remove avatar
<% end %>

If you want to remove the file manually, you can call remove_avatar!, then save the object.

#=> true

Uploading files from a remote location

Your users may find it convenient to upload a file from a location on the Internet via a URL. CarrierWave makes this simple, just add the appropriate attribute to your form and you're good to go:

<%= form_for @user, html: { multipart: true } do |f| %>
    <label>My Avatar URL:</label>
    <%= image_tag(@user.avatar_url) if @user.avatar? %>
    <%= f.text_field :remote_avatar_url %>
<% end %>

If you're using ActiveRecord, CarrierWave will indicate invalid URLs and download failures automatically with attribute validation errors. If you aren't, or you disable CarrierWave's validate_download option, you'll need to handle those errors yourself.

Providing a default URL

In many cases, especially when working with images, it might be a good idea to provide a default url, a fallback in case no file has been uploaded. You can do this easily by overriding the default_url method in your uploader:

class MyUploader < CarrierWave::Uploader::Base
  def default_url(*args)
    "/images/fallback/" + [version_name, "default.png"].compact.join('_')

Or if you are using the Rails asset pipeline:

class MyUploader < CarrierWave::Uploader::Base
  def default_url(*args)
    ActionController::Base.helpers.asset_path("fallback/" + [version_name, "default.png"].compact.join('_'))

Recreating versions

You might come to a situation where you want to retroactively change a version or add a new one. You can use the recreate_versions! method to recreate the versions from the base file. This uses a naive approach which will re-upload and process the specified version or all versions, if none is passed as an argument.

When you are generating random unique filenames you have to call save! on the model after using recreate_versions!. This is necessary because recreate_versions! doesn't save the new filename to the database. Calling save! yourself will prevent that the database and file system are running out of sync.

instance =
instance.recreate_versions!(:thumb, :large)

Or on a mounted uploader:

User.find_each do |user|

Note: recreate_versions! will throw an exception on records without an image. To avoid this, scope the records to those with images or check if an image exists within the block. If you're using ActiveRecord, recreating versions for a user avatar might look like this:

User.find_each do |user|
  user.avatar.recreate_versions! if user.avatar?

Configuring CarrierWave

CarrierWave has a broad range of configuration options, which you can configure, both globally and on a per-uploader basis:

CarrierWave.configure do |config|
  config.permissions = 0666
  config.directory_permissions = 0777 = :file

Or alternatively:

class AvatarUploader < CarrierWave::Uploader::Base
  permissions 0777

If you're using Rails, create an initializer for this:


If you want CarrierWave to fail noisily in development, you can change these configs in your environment file:

CarrierWave.configure do |config|
  config.ignore_integrity_errors = false
  config.ignore_processing_errors = false
  config.ignore_download_errors = false

Testing with CarrierWave

It's a good idea to test your uploaders in isolation. In order to speed up your tests, it's recommended to switch off processing in your tests, and to use the file storage. In Rails you could do that by adding an initializer with:

if Rails.env.test? or Rails.env.cucumber?
  CarrierWave.configure do |config| = :file
    config.enable_processing = false

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.

CarrierWave comes with some RSpec matchers which you may find useful:

require 'carrierwave/test/matchers'

describe MyUploader do
  include CarrierWave::Test::Matchers

  let(:user) { double('user') }
  let(:uploader) {, :avatar) }

  before do
    MyUploader.enable_processing = true { |f|!(f) }

  after do
    MyUploader.enable_processing = false

  context 'the thumb version' do
    it "scales down a landscape image to be exactly 64 by 64 pixels" do
      expect(uploader.thumb).to have_dimensions(64, 64)

  context 'the small version' do
    it "scales down a landscape image to fit within 200 by 200 pixels" do
      expect(uploader.small).to be_no_larger_than(200, 200)

  it "makes the image readable only to the owner and not executable" do
    expect(uploader).to have_permissions(0600)

  it "has the correct format" do
    expect(uploader).to be_format('png')

Setting the enable_processing flag on an uploader will prevent any of the versions from processing as well. Processing can be enabled for a single version by setting the processing flag on the version like so:

@uploader.thumb.enable_processing = true


If you want to use fog you must add in your CarrierWave initializer the following lines

config.fog_provider = 'fog' # 'fog/aws' etc. Defaults to 'fog'
config.fog_credentials = { ... } # Provider specific credentials

Using Amazon S3

Fog AWS is used to support Amazon S3. Ensure you have it in your Gemfile:

gem "fog-aws"

You'll need to provide your fog_credentials and a fog_directory (also known as a bucket) in an initializer. For the sake of performance it is assumed that the directory already exists, so please create it if it needs to be. You can also pass in additional options, as documented fully in lib/carrierwave/storage/fog.rb. Here's a full example:

CarrierWave.configure do |config|
  config.fog_provider = 'fog/aws'                        # required
  config.fog_credentials = {
    provider:              'AWS',                        # required
    aws_access_key_id:     'xxx',                        # required
    aws_secret_access_key: 'yyy',                        # required
    region:                'eu-west-1',                  # optional, defaults to 'us-east-1'
    host:                  '',             # optional, defaults to nil
    endpoint:              '' # optional, defaults to nil
  config.fog_directory  = 'name_of_directory'                                   # required
  config.fog_public     = false                                                 # optional, defaults to true
  config.fog_attributes = { cache_control: "public, max-age=#{365.days.to_i}" } # optional, defaults to {}

In your uploader, set the storage to :fog

class AvatarUploader < CarrierWave::Uploader::Base
  storage :fog

That's it! You can still use the CarrierWave::Uploader#url method to return the url to the file on Amazon S3.

Using Rackspace Cloud Files

Fog is used to support Rackspace Cloud Files. Ensure you have it in your Gemfile:

gem "fog"

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.

Using a US-based account:

CarrierWave.configure do |config|
  config.fog_provider = "fog/rackspace/storage"   # optional, defaults to "fog"
  config.fog_credentials = {
    provider:           'Rackspace',
    rackspace_username: 'xxxxxx',
    rackspace_api_key:  'yyyyyy',
    rackspace_region:   :ord                      # optional, defaults to :dfw
  config.fog_directory = 'name_of_directory'

Using a UK-based account:

CarrierWave.configure do |config|
  config.fog_provider = "fog/rackspace/storage"   # optional, defaults to "fog"
  config.fog_credentials = {
    provider:           'Rackspace',
    rackspace_username: 'xxxxxx',
    rackspace_api_key:  'yyyyyy',
    rackspace_auth_url: Fog::Rackspace::UK_AUTH_ENDPOINT,
    rackspace_region:   :lon
  config.fog_directory = 'name_of_directory'

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.

config.asset_host = ""

In your uploader, set the storage to :fog

class AvatarUploader < CarrierWave::Uploader::Base
  storage :fog

That's it! You can still use the CarrierWave::Uploader#url method to return the url to the file on Rackspace Cloud Files.

Using Google Storage for Developers

Fog is used to support Google Storage for Developers. Ensure you have it in your Gemfile:

gem "fog-google"
gem "google-api-client", "> 0.8.5", "< 0.9"
gem "mime-types"

You'll need to configure a directory (also known as a bucket), access key id and secret access key in the initializer. For the sake of performance it is assumed that the directory already exists, so please create it if need be.

Please read the fog-google README on how to get credentials.

CarrierWave.configure do |config|
  config.fog_provider = 'fog/google'                        # required
  config.fog_credentials = {
    provider:                         'Google',
    google_storage_access_key_id:     'xxxxxx',
    google_storage_secret_access_key: 'yyyyyy'
  config.fog_directory = 'name_of_directory'

In your uploader, set the storage to :fog

class AvatarUploader < CarrierWave::Uploader::Base
  storage :fog

That's it! You can still use the CarrierWave::Uploader#url method to return the url to the file on Google.

Optimized Loading of Fog

Since Carrierwave doesn't know which parts of Fog you intend to use, it will just load the entire library (unless you use e.g. [fog-aws, fog-google] instead of fog proper). 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. Ex:

gem "fog", "~> 1.27", require: "fog/rackspace/storage"
gem "carrierwave"

A couple of notes about versions:

  • This functionality was introduced in Fog v1.20.
  • This functionality is slated for CarrierWave v1.0.0.

If you're not relying on Gemfile entries alone and are requiring carrierwave anywhere, ensure you require fog/rackspace/storage before it. Ex:

require "fog/rackspace/storage"
require "carrierwave"

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.

When in doubt, inspect Fog.constants to see what has been loaded.

Dynamic Asset Host

The asset_host config property can be assigned a proc (or anything that responds to call) for generating the host dynamically. The proc-compliant object gets an instance of the current CarrierWave::Storage::Fog::File or CarrierWave::SanitizedFile as its only argument.

CarrierWave.configure do |config|
  config.asset_host = proc do |file|
    identifier = # some logic

Using RMagick

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:

class AvatarUploader < CarrierWave::Uploader::Base
  include CarrierWave::RMagick

The RMagick module gives you a few methods, like CarrierWave::RMagick#resize_to_fill which manipulate the image file in some way. 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.

class AvatarUploader < CarrierWave::Uploader::Base
  include CarrierWave::RMagick

  process resize_to_fill: [200, 200]
  process convert: 'png'

  def filename
    super.chomp(File.extname(super)) + '.png' if original_filename.present?

Check out the manipulate! method, which makes it easy for you to write your own manipulation methods.

Using MiniMagick

MiniMagick is similar to RMagick but performs all the operations using the 'mogrify' command which is part of the standard ImageMagick kit. This allows you to have the power of ImageMagick without having to worry about installing all the RMagick libraries.

See the MiniMagick site for more details:

And the ImageMagick command line options for more for whats on offer:

Currently, the MiniMagick carrierwave processor provides exactly the same methods as for the RMagick processor.

class AvatarUploader < CarrierWave::Uploader::Base
  include CarrierWave::MiniMagick

  process resize_to_fill: [200, 200]

Migrating from Paperclip

If you are using Paperclip, you can use the provided compatibility module:

class AvatarUploader < CarrierWave::Uploader::Base
  include CarrierWave::Compatibility::Paperclip

See the documentation for CarrierWave::Compatibility::Paperclip for more details.

Be sure to use mount_on to specify the correct column:

mount_uploader :avatar, AvatarUploader, mount_on: :avatar_file_name


The Active Record validations use the Rails i18n framework. Add these keys to your translations file:

    carrierwave_processing_error: failed to be processed
    carrierwave_integrity_error: is not of an allowed file type
    carrierwave_download_error: could not be downloaded
    extension_whitelist_error: "You are not allowed to upload %{extension} files, allowed types: %{allowed_types}"
    extension_blacklist_error: "You are not allowed to upload %{extension} files, prohibited types: %{prohibited_types}"
    content_type_whitelist_error: "You are not allowed to upload %{content_type} files"
    content_type_blacklist_error: "You are not allowed to upload %{content_type} files"
    rmagick_processing_error: "Failed to manipulate with rmagick, maybe it is not an image?"
    mini_magick_processing_error: "Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: %{e}"
    min_size_error: "File size should be greater than %{min_size}"
    max_size_error: "File size should be less than %{max_size}"

The carrierwave-i18n library adds support for additional locales.

Large files

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.

You may change this behavior by overriding either or both of the move_to_cache and move_to_store methods:

class MyUploader < CarrierWave::Uploader::Base
  def move_to_cache

  def move_to_store

When the move_to_cache and/or move_to_store methods return true, files will be moved (instead of copied) to the cache and store respectively.

This has only been tested with the local filesystem store.

Skipping ActiveRecord callbacks

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

class User
  mount_uploader :avatar, AvatarUploader

Will add these callbacks:

after_save :store_avatar!
before_save :write_avatar_identifier
after_commit :remove_avatar!, on: :destroy
after_commit :mark_remove_avatar_false, on: :update
after_save :store_previous_changes_for_avatar
after_commit :remove_previously_stored_avatar, on: :update

If you want to skip any of these callbacks (eg. you want to keep the existing avatar, even after uploading a new one), you can use ActiveRecords skip_callback method.

class User
  mount_uploader :avatar, AvatarUploader
  skip_callback :commit, :after, :remove_previously_stored_avatar

Contributing to CarrierWave



Copyright (c) 2008-2015 Jonas Nicklas

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.


carrierwave open issues Ask a question     (View All Issues)
  • almost 3 years Files remove in nested forms for 0.11
  • almost 3 years SourceClear raising a vulnerability for Carrierwave
  • almost 3 years Letter url is null after save
  • almost 3 years Performance drop of vs.
  • almost 3 years Uploading via a nested form doesn't seem to be working
  • almost 3 years Carrierwave not logging errors.
  • almost 3 years Generated X-Amz-Expires is incorrect when it spans a transition to/off Daylight Savings Time
  • almost 3 years Hard to determine whether a potential file already exists!
  • almost 3 years Uploading data:image/png;base64 instead of select image or from url
  • almost 3 years Support for pre-signed upload URLs
  • almost 3 years Frozen NilClass error when overwriting filename method
  • almost 3 years Avatar URL not working with Carrierwave 1.0.0.beta
  • about 3 years Removing single image when using multiple file uploads feature, doesn't work when only one image left
  • about 3 years Different versions are not uploaded to S3 (Using Fog storage)
  • about 3 years Migrate single upload to multiple upload in same model
  • about 3 years remove_file: removes file even if parameter is '0'
  • about 3 years Uploading other images when getting error
  • about 3 years Support aws instance profile / role based access
  • about 3 years In a multiple file upload I seem not to be able to delete the last file properly.
  • about 3 years Custom domain for protected assets on AWS s3
  • about 3 years Carrierwave is not storing images locally to Rails public folder after processing
  • about 3 years Assigning photo attribute saves as ActionDispatch::Http:UploadedFile
  • about 3 years ActiveRecord's reload method doesn't always reload carrierwave attributes
  • about 3 years CarrierWave sets wrong content type on XLSX files
  • about 3 years [question] Directly set URL on model
  • about 3 years Can not delete all images on a upload that handles multiple files
  • about 3 years How to setup private files with CloudFront?
  • about 3 years remote_XXX_url not reading correct content-type when extension is not provided
  • about 3 years Invalid locale in CarrierWave::MiniMagick#manipulate!
  • over 3 years Support for ActiveRecord dup method
carrierwave open pull requests (View All Pulls)
  • regard :from_version option on calling #recreate_versions! with args
  • Remove locales from main repository
  • Run MRI 2.3 on Travis CI
  • Replace instance variables by `let` in `sanitized_file_spec.rb`
  • Upgrade testing tools
  • Update CHANGELOG with post-0.10.0 changes
  • Normalize gem version
  • Don't raise an error when content_type is called on a deleted file
  • Backport rspec3 matcher protocol deprecation fix
  • Backport content type whitelist/blacklist translations
  • Mitigate against CVE-2016-3714 (ImageTragick)
  • Include the asset_host in default_url if it returns a relative url
  • Do not allow file type spoofing if the header bytes are not recognized
  • 0.11 Closing file after mime-type checking
  • Define methods instead of alias
  • Remove 'config.fog_provider' from the 'Using Amazon S3' section.
  • Update
  • Edit readme: clarify writing conditional methods
  • Fix typo in Google Storage for Developers session
  • Update zh-CN.yml rename whitelist & blacklist
  • Add vi locale
  • Changed public URL method to support empty fog_directory.
  • README update for Skipping ActiveRecord callbacks
  • Close file in SanitizedFile#mime_magic_content_type
  • Use Ruby v2.3.1 instead of v2.3.0
  • Adding Arabic locale
  • use File.exist? not File.exists? as it's depricated
  • Headers for download by url
  • Add support for callbacks on :proccess
  • Don't error if updated record
  • 0.11 stable
  • 0.10 stable
  • [skip ci] Wip on downloader strategies
  • Allow non-argument options to be passed in mini magick combine_options
  • Fix #1755
  • Fixing #1889 Cache ID should not fail from negative time stamp
  • Fix args of `default_url` in templates
  • Fixing #1977 Invalid locale in CarrierWave::MiniMagick#manipulate!
  • Update README: remove version specifier for fog
  • Optimization: avoid calling `file.url` twice.
  • mini_magick_image now reads file stream
  • Add fog_serve_public as an override
  • Update nokogiri to 1.7.1
  • JSON nested mount
  • Remove potentially redundant HEAD request
  • Decode unicode filenames from URL
  • Allow some URI-compatibility, reveal latent bug w/ tests
  • Allow read to accept bytes as parameter
  • Replace send with __send__
  • Added Proc Support for Width and Height
  • Add allowed_types to content_type_whitelist_error
  • Fix #serializable_hash to returns string keys for versions
  • Manage transaction rollback
  • Update
  • Add `use_iam_profile` aws config parameter
  • Replace mime-types gem with mini_mime
carrierwave questions on Stackoverflow (View All Questions)
  • How to Download and Store Remote Image URLs with Carrierwave
  • Rails count number of all Carrierwave uploaded files
  • Carrierwave uploader consuming memroy
  • Rails 4 Carrierwave + Minimagick: Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: `mogrify -crop
  • Rails Tutorial Chapter 11. Carrierwave and Cloudinary. Heroku application Error
  • Memory Allocation Error when uploading large file to Rails app with Carrierwave
  • Carrierwave thumb method doesn't work for remote image url
  • Rails ActiveAdmin with carrierwave
  • CarrierWave Backgrounder not uploading versions images to AWS S3
  • Send_file aws s3 carrierwave
  • CarrierWave not saving properly with Monologue Posts
  • carrierwave same callback for multiple uploaders
  • undefined method `enqueue_active_job' for CarrierWave::Backgrounder:Module)
  • Define Carrierwave process size in model attributes
  • Lots of difficulty integrating jquery-file-uploader with carrierwave in my rails app
  • Getting file size of carrierwave upload
  • Rails4: How do I store images uploaded by carrierwave in private folder?
  • Issue using carrierwave: uploaded images disappear after refresh
  • carrierwave javascript to show image across page refreshes not working
  • CarrierWave Video - Transcoding passes but video not uploading
  • Howto tell Carrierwave remote_image_url to use a http proxy server
  • How to hide actual path Carrierwave
  • can not download a document on S3 versioning with carrierwave
  • Carrierwave Multiple File Upload + No implicit conversion of nil into String
  • Carrierwave files not uploading Rails4
  • CarrierWave custom validation bug Rails
  • Carrierwave, creating a duplicate attachment when duplicating its containing model
  • Multiple file upload with carrierwave
  • Use carrierwave with Bearer token Authorization
  • Rails 4 carrierwave gem TypeError on assign to uploader
carrierwave list of languages used
carrierwave latest release notes
v0.10.0 v0.10.0
  • [changed] Memoize uploaders and uploader_options (Derek Parker and Joshua Davey from Hashrocket)
  • [changed] Don't force pad background color to white in resize_and_pad (@fnordfish)
  • [changed] Remove auth access information when parsing URL for filename (@nddeluca)
  • [changed] Read Content type from cached and uploaded file, adds mime-types as hard dependency
  • [added] Added authenticated_url functionality for Openstack storage (@snoopie)
  • [added] Add Polish I18n translations for errors (@ArturT)
  • [added] Add Greek locale for error messages (@agorf)
  • [added] Add French locale for error messages (@gdurelle)
  • [added] Add Japanese locale for error messages (@tomodian)
  • [added] Add Norwegian locale for error messages (@theodorton)
  • [added] Add Portuguese locale for error messages (@pedrosmmoreira)
  • [fixed] Overridden serializable_hash accepts an options hash (@bensie)
  • [fixed] Fog connection object performance issues (@taavo)
  • [fixed] Delete Tempfile after manipulate with MiniMagick (@dimko)
  • [fixed] Ensure #remove_#{column} and #remove_#{column} return false after committing with ActiveRecord (@bensie)
  • [fixed] Fix issue with content-disposition existing with no filename when downloading, reports that Google does this (@hasghari / @bensie / @taavo)
v0.9.0 v0.9.0
  • [BREAKING CHANGE] Use integer time (UTC) to generate cache IDs [@bensie]
  • [changed] Recommend using ActionController::Base.helpers instead of Sprockets::Rails::Helper for asset pipeline [@c0]
  • [changed] Lots of URL encoding fixes [@taavo]
  • [added] Added #version_exists? method [@tmaier]
  • [added] Added configuration param (:fog_use_ssl_for_aws) to disable SSL for public_url [@pbzymek]
  • [added] Add Dutch i18n translations for errors [@vanderhoorn]
  • [added] Add Czech i18n translations for errors [@elmariofredo]
  • [added] Add German i18n translations for errors [@felixbuenemann]
  • [fixed] Gemspec error in Ruby 2.0.0 [@sanemat]
  • [fixed] Fixed bug in serializing to xml or json where both :only and :except are passed [@Knack]
  • [fixed] Fix recreate_versions! when version if proc returns false [@arthurnn]
v0.6.0 v0.6.0
  • [BREAKING CHANGE] Require Rails 3.2 or Rails master (4.0) - depends on activesupport/activemodel [bensie]
  • [BREAKING CHANGE] Remove :S3 storage option in favor of Fog [bensie]
  • [BREAKING CHANGE] Remove :CloudFiles storage option in favor of Fog [bensie]
  • [changed] JSON / XML serialization hashes are consistent and work as expected with ActiveRecord's serializable_hash [bensie]
  • [added] fog_host now accepts a proc (useful for dynamic asset servers) [jtrim]
  • [added] Add ability to process a version from an existing version so you aren't always crunching the original, large file [ferblape]
  • [added] Allow brackets in remote URLs [ngauthier]
  • [added] CarrierWave::Storage::Fog::File#exists? to check the existence of the file without needing to fetch it [bensie]
  • [added] Gravity option on resize_to_fill (minimagick) [TheOddLinguist]
  • [added] Add query options for s3 to support response headers overwriting [meceo]
  • [added] Make storages File#url methods to work without any params [meceo]
  • [added] Set the CarrierWave.root correctly if Padrino is defined [futurechimp]
  • [added] Cache fog connections for improved performance [labocho]
  • [fixed] Fix slow fetching of content-length on remote file [geemus]
  • [fixed] Fog remote specs now passing and depend on Fog >= 1.3.1 [geemus]
  • [fixed] Fix an issue where multi-page PDFs can't be converted with RMagick [chanind]
  • [fixed] MiniMagick expects string args to mogrify commands [bensie]
  • [fixed] With Active Record ORM, setting remote_url marks mounted column as dirty [trevorturk]
  • [fixed] Fix possible race condition with CarrierWave.root [bensie]
  • [fixed] ActiveSupport::Memoizable deprecation warning [slbug]
Other projects in Ruby