RubyGems - card - Versions diffs - 1.19.3 → 1.19.4 - Mend

card 1.19.3 → 1.19.4

Files changed (190) hide show

data/vendor/carrierwave/.travis.yml DELETED

@@ -1,58 +0,0 @@
-language: ruby
-cache: bundler
-rvm:
- - 2.0
- - 2.1
- - 2.2.5
- - 2.3.1
- - ruby-head
- - jruby
- - jruby-head
-env:
-  global:
-    - JRUBY_OPTS="--2.0"
-gemfile:
-  - Gemfile
-  - gemfiles/rails-4-0-stable.gemfile
-  - gemfiles/rails-4-1-stable.gemfile
-  - gemfiles/rails-4-2-stable.gemfile
-  - gemfiles/rails-master.gemfile
-sudo: false
-before_script:
-  - psql -c 'create database carrierwave_test;' -U postgres
-matrix:
-  exclude:
-    - rvm: 2.0
-      gemfile: Gemfile
-    - rvm: 2.0
-      gemfile: gemfiles/rails-master.gemfile
-    - rvm: 2.1
-      gemfile: Gemfile
-    - rvm: 2.1
-      gemfile: gemfiles/rails-master.gemfile
-    - rvm: jruby
-      gemfile: Gemfile
-    - rvm: jruby
-      gemfile: gemfiles/rails-master.gemfile
-    - rvm: jruby-head
-      gemfile: gemfiles/rails-master.gemfile
-  allow_failures:
-    - rvm: ruby-head
-    - rvm: jruby-head
-    - gemfile: gemfiles/rails-master.gemfile
-  fast_finish: true
-notifications:
-  email: false
-  slack:
-    secure: Npzanyv/LXLIRlrNs8iTUbZNRhXlP+K2ZpjZoS2UKkr09jYyP1qdf5a//R3Lu7Yat7g2b4qTJGbaZBEMUQSVaJ6UX6quiBJjVWxjxjQ4Ugk8k/yOIAcGEGYPfS6YzRXemRwo9j4uy76cmwlv8cwEuYTSTBRK4XrdYHslX6pKSXM=
-addons:
-  postgresql: "9.3"

data/vendor/carrierwave/CHANGELOG.md DELETED

@@ -1,81 +0,0 @@
-# Carrierwave History/Changelog
-All notable changes to this project will be documented in this file.
-This project adheres to [Semantic Versioning](http://semver.org/).
-## [Unreleased]
-### Added
-* Add a test matcher for the format (@yanivpr [#1758](https://github.com/carrierwaveuploader/carrierwave/pull/1758))
-* Support of MiniMagick's Combine options (@bernabas [#1754](https://github.com/carrierwaveuploader/carrierwave/pull/1754))
-* Validate with the actual content-type of files (@eavgerinos)
-* Support for multiple file uploads with `mount_uploaders` method (@jnicklas and @lisarutan [#1481](https://github.com/carrierwaveuploader/carrierwave/pull/1481))
-* Add a `cache_only` configuration option, useful for testing (@jeffkreeftmeijer [#1456](https://github.com/carrierwaveuploader/carrierwave/pull/1456))
-* Add `#width` and `#height` methods to MiniMagick processor (@ShivaVS [#1405](https://github.com/carrierwaveuploader/carrierwave/pull/1405))
-* Add `#width` and `#height` methods to the RMagick processor (@mehlah [#1805](https://github.com/carrierwaveuploader/carrierwave/pull/1805))
-* Support for jRuby (@lephyrius [#1377](https://github.com/carrierwaveuploader/carrierwave/pull/1377))
-* Make cache storage configurable (@mshibuya [#1312](https://github.com/carrierwaveuploader/carrierwave/pull/1312))
-* Errors on file size (@gautampunhani [#1026](https://github.com/carrierwaveuploader/carrierwave/pull/1026))
-* Add Indonesian, Taiwanese and Chinese i18n translations for errors (@saveav, @st0012, @msyesyan)
-### Changed
-* [BREAKING CHANGE] Allow non-ASCII filename by default (@shuhei [#1772](https://github.com/carrierwaveuploader/carrierwave/pull/1772))
-* [BREAKING CHANGE] `to_json` behavior changed when serializing an uploader (@jnicklas and @lisarutan [#1481](https://github.com/carrierwaveuploader/carrierwave/pull/1481))
-* [BREAKING CHANGE] Rename `extension_white_list` ~> `extension_whitelist` (@mehlah [#1819](https://github.com/carrierwaveuploader/carrierwave/pull/1819))
-* [BREAKING CHANGE] Rename `extension_black_list` ~> `extension_blacklist` (@mehlah [#1819](https://github.com/carrierwaveuploader/carrierwave/pull/1819))
-* [BREAKING CHANGE] Rename i18n keys `extension_black_list_error` ~> `extension_blacklist_error` and `extension_white_list_error` ~> `extension_whitelist_error` (@mehlah)
-* Better error when the configured storage is unknown (@st0012 [#1779](https://github.com/carrierwaveuploader/carrierwave/pull/1779))
-* Allow to pass additionnal options to Rackspace `authenticated_url` (@duhast [#1722](https://github.com/carrierwaveuploader/carrierwave/pull/1722))
-* Reduced memory footprint (@schneems [#1652](https://github.com/carrierwaveuploader/carrierwave/pull/1652), @simonprev [#1706](https://github.com/carrierwaveuploader/carrierwave/pull/1706))
-* Improve Fog Loading (@plribeiro3000 [#1620](https://github.com/carrierwaveuploader/carrierwave/pull/1620), @eavgerinos)
-* All locales from `config.i18n.available_locales` are added to load_path (@printercu [#1521](https://github.com/carrierwaveuploader/carrierwave/pull/1521))
-* Do not display RMagick exception in I18n message (manuelpradal [#1361](https://github.com/carrierwaveuploader/carrierwave/pull/1361))
-* `#default_url` now accepts the same args passed to `#url` (@shekibobo [#1347](https://github.com/carrierwaveuploader/carrierwave/pull/1347))
-* Accept an array of strings or regexps to white/blacklist content types (@mehlah [#1816](https://github.com/carrierwaveuploader/carrierwave/pull/1816))
-* `#content_type_whitelist` and `extension_whitelist` now takes either a string, a regexp, or an array of values (same thing for blacklists) (@mehlah [#1825](https://github.com/carrierwaveuploader/carrierwave/pull/1825))
-* Blank uploaders are now memoized on the model instance (@DarthSim [#1860](https://github.com/carrierwaveuploader/carrierwave/pull/1860))
-### Removed
-* Remove `CarrierWave::MimeTypes` processor module (@mehlah [#1813](https://github.com/carrierwaveuploader/carrierwave/pull/1813))
-* Remove `CarrierWave::MagicMimeTypes` processor module (@mehlah [#1816](https://github.com/carrierwaveuploader/carrierwave/pull/1816))
-* Remove dependency on `ruby-filemagic` in white/blacklist content types (@mehlah [#1816](https://github.com/carrierwaveuploader/carrierwave/pull/1816))
-### Fixed
-* Fix `Mounter.blank?` method (@Bonias [#1746](https://github.com/carrierwaveuploader/carrierwave/pull/1746))
-* Reset `remove_#{column}` after invoking `remove_#{column}` (@eavgerinos [#1668](https://github.com/carrierwaveuploader/carrierwave/pull/1668))
-* Change Google's url to the `public_url` (@m7moud [#1683](https://github.com/carrierwaveuploader/carrierwave/pull/1683))
-* Do not write to `ActiveModel::Dirty` changes when assigning something blank to a mounter that was originally blank (@eavgerinos [#1635](https://github.com/carrierwaveuploader/carrierwave/pull/1635))
-* Various grammar and typos fixes to error messages translations
-* Don't error when size is called on a deleted file (@danielevans [#1561](https://github.com/carrierwaveuploader/carrierwave/pull/1561))
-* Flush mounters on `#dup` of active record model (@danielevans [#1544](https://github.com/carrierwaveuploader/carrierwave/pull/1544))
-* `Fog::File.read` returns its contents after upload instead of "closed stream" error (@stormsilver [#1517](https://github.com/carrierwaveuploader/carrierwave/pull/1517))
-* Don't read file twice when calling `sanitized_file` or `cache!` (@felixbuenemann [#1476](https://github.com/carrierwaveuploader/carrierwave/pull/1476))
-* Change image extension when converting formats (@nashby [#1446](https://github.com/carrierwaveuploader/carrierwave/pull/1446))
-* Fix file delete being called twice on remove (@adamcrown [#1441](https://github.com/carrierwaveuploader/carrierwave/pull/1441))
-* RSpec 3 support (@randoum #1421[](https://github.com/carrierwaveuploader/carrierwave/pull/1421), @akiomik [#1370](https://github.com/carrierwaveuploader/carrierwave/pull/1370))
-* MiniMagick convert to a format all the pages by default and accept an optional page number parameter to convert specific pages (@harikrishnan83 [#1408](https://github.com/carrierwaveuploader/carrierwave/pull/1408))
-* Fix cache workfile collision between versions (@jvdp [#1399](https://github.com/carrierwaveuploader/carrierwave/pull/1399))
-* Reset mounter cache on record reload (@semenyukdmitriy [#1383](https://github.com/carrierwaveuploader/carrierwave/pull/1383))
-* Retrieve only active versions of files (@filipegiusti [#1351](https://github.com/carrierwaveuploader/carrierwave/pull/1351))
-* Fix default gravity in MiniMagick `resize_and_pad` (@abevoelker [#1358](https://github.com/carrierwaveuploader/carrierwave/pull/1358))
-* Skip loading RMagick if already loaded (@mshibuya [#1346](https://github.com/carrierwaveuploader/carrierwave/pull/1346))
-* Make the `#remove_#{column}` accessor set the mounted column as changed (@nikz [#1326](https://github.com/carrierwaveuploader/carrierwave/pull/1326))
-* Tempfile and @content_type assignment (@bensie [#1487](https://github.com/carrierwaveuploader/carrierwave/issues/1487))
-## 0.11.0 - 2016-03-29
-### Added
-### Changed
-* `cache_id` is now less collision-prone thanks to a counter (@stillwaiting and @mtsmfm [#1866](https://github.com/carrierwaveuploader/carrierwave/pull/1866))
-### Removed
-### Fixed
-* Fix require RMagick deprecation warning (@thomasfedb and @bensie [#1788](https://github.com/carrierwaveuploader/carrierwave/pull/1788))
-## 0.10.0 - 2014-02-26
-Please check [0.10-stable] for previous changes.
-[0.10-stable]: https://github.com/carrierwaveuploader/carrierwave/blob/0.10-stable/History.txt

data/vendor/carrierwave/CONTRIBUTING.md DELETED

@@ -1,37 +0,0 @@
-# Contributing to CarrierWave
-CarrierWave thrives on a large number of [contributors](https://github.com/carrierwaveuploader/carrierwave/contributors),
-and pull requests are very welcome. Before submitting a pull request, please make sure that your changes are well tested.
-First, make sure you have `imagemagick` and `ghostscript` installed. You may need `libmagic` as well.
-Then, you'll need to install bundler and the gem dependencies:
-  `gem install bundler && bundle install`
-You should now be able to run the local tests:
-  `bundle exec rake`
-You can also run the remote specs by creating a ~/.fog file:
-```yaml
-:carrierwave:
-  :aws_access_key_id: xxx
-  :aws_secret_access_key: yyy
-  :rackspace_username: xxx
-  :rackspace_api_key: yyy
-  :google_storage_access_key_id: xxx
-  :google_storage_secret_access_key: yyy
-```
-You should now be able to run the remote tests:
-    REMOTE=true bundle exec rake
-Please test with the latest Ruby 2.2.x version using RVM if possible.
-## Running active record tests
-Make sure you have a local PostgreSQL database named `carrierwave_test` with the username
-`postgres`

data/vendor/carrierwave/Gemfile DELETED

@@ -1,5 +0,0 @@
-source "https://rubygems.org"
-gem "activemodel-serializers-xml"
-gemspec

data/vendor/carrierwave/README.md DELETED

@@ -1,995 +0,0 @@
-# CarrierWave
-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](https://travis-ci.org/carrierwaveuploader/carrierwave.svg?branch=master)](http://travis-ci.org/carrierwaveuploader/carrierwave)
-[![Code Climate](http://img.shields.io/codeclimate/github/carrierwaveuploader/carrierwave.svg)](https://codeclimate.com/github/carrierwaveuploader/carrierwave)
-> ## carrierwave version disclaimer
-> ***This README is for a branch which is still in development.
-> Please switch to latest `0.x` branch for stable version.***
-## Information
-* RDoc documentation [available on RubyDoc.info](http://rubydoc.info/gems/carrierwave/frames)
-* Source code [available on GitHub](http://github.com/carrierwaveuploader/carrierwave)
-* More information, known limitations, and how-tos [available on the wiki](https://github.com/carrierwaveuploader/carrierwave/wiki)
-## Getting Help
-* Please ask the community on [Stack Overflow](http://stackoverflow.com/) for help if you have any questions. Please do not post usage questions on the issue tracker.
-* Please report bugs on the [issue tracker](http://github.com/carrierwaveuploader/carrierwave/issues) but read the "getting help" section in the wiki first.
-## Installation
-Install the latest stable release:
-```
-$ gem install carrierwave
-```
-In Rails, add it to your Gemfile:
-```ruby
-gem 'carrierwave'
-```
-Finally, restart the server to apply the changes.
-As of version 1.0.0 (forthcoming), 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:
-	app/uploaders/avatar_uploader.rb
-Check out this file for some hints on how you can customize your uploader. It
-should look something like this:
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  storage :file
-end
-```
-You can use your uploader class to store and retrieve files like this:
-```ruby
-uploader = AvatarUploader.new
-uploader.store!(my_file)
-uploader.retrieve_from_store!('my_file.png')
-```
-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:
-### ActiveRecord
-Make sure you are loading CarrierWave after loading your ORM, otherwise you'll
-need to require the relevant extension manually, e.g.:
-```ruby
-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:
-```ruby
-class User < ActiveRecord::Base
-  mount_uploader :avatar, AvatarUploader
-end
-```
-Now you can cache files by assigning them to the attribute, they will
-automatically be stored when the record is saved.
-```ruby
-u = User.new
-u.avatar = params[:file] # Assign a file like this, or
-# like this
-File.open('somewhere') do |f|
-  u.avatar = f
-end
-u.save!
-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:
-* [carrierwave-datamapper](https://github.com/carrierwaveuploader/carrierwave-datamapper)
-* [carrierwave-mongoid](https://github.com/carrierwaveuploader/carrierwave-mongoid)
-* [carrierwave-sequel](https://github.com/carrierwaveuploader/carrierwave-sequel)
-There are more extensions listed in [the wiki](https://github.com/carrierwaveuploader/carrierwave/wiki)
-## Multiple file uploads
-**Note:** You must specify using the master branch to enable this feature:
-`gem 'carrierwave', github: 'carrierwaveuploader/carrierwave'`.
-CarrierWave also has convenient support for multiple file upload fields.
-### ActiveRecord
-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:
-	rails g migration add_avatars_to_users avatars:json
-	rake db:migrate
-Open your model file and mount the uploader:
-```ruby
-class User < ActiveRecord::Base
-  mount_uploaders :avatars, AvatarUploader
-end
-```
-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:
-```erb
-<%= 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:
-```ruby
-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.
-```ruby
-u = User.new(params[:user])
-u.save!
-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:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def store_dir
-    'public/my/upload/directory'
-  end
-end
-```
-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:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def cache_dir
-    '/tmp/projectname-cache'
-  end
-end
-```
-## 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.
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def extension_whitelist
-    %w(jpg jpeg gif png)
-  end
-end
-```
-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
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def content_type_whitelist
-    /image\//
-  end
-end
-```
-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
-```ruby
-class NoJsonUploader < CarrierWave::Uploader::Base
-  def content_type_blacklist
-    ['application/text', 'application/json']
-  end
-end
-```
-### Filenames and unicode chars
-Another security issue you should care for is the file names (see
-[Ruby On Rails Security Guide](http://guides.rubyonrails.org/security.html#file-uploads)).
-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.
-```ruby
-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
-```
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  include CarrierWave::MiniMagick
-  process resize_to_fit: [800, 800]
-  version :thumb do
-    process resize_to_fill: [200,200]
-  end
-end
-```
-When this uploader is used, an uploaded image would be scaled to be no larger
-than 800 by 800 pixels. A version called thumb is then created, which is scaled
-and cropped to exactly 200 by 200 pixels. The uploader could be used like this:
-```ruby
-uploader = AvatarUploader.new
-uploader.store!(my_file)                              # size: 1024x768
-uploader.url # => '/url/to/my_file.png'               # size: 800x600
-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:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  version :animal do
-    version :human
-    version :monkey
-    version :llama
-  end
-end
-```
-### Conditional versions
-Occasionally you want to restrict the creation of versions on certain
-properties within the model or based on the picture itself.
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  version :human, if: :is_human?
-  version :monkey, if: :is_monkey?
-  version :banner, if: :is_landscape?
-private
-  def is_human? picture
-    model.can_program?(:ruby)
-  end
-  def is_monkey? picture
-    model.favorite_food == 'banana'
-  end
-  def is_landscape? picture
-    image = MiniMagick::Image.open(picture.path)
-    image[:width] > image[:height]
-  end
-end
-```
-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.
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  version :thumb do
-    process resize_to_fill: [280, 280]
-  end
-  version :small_thumb, from_version: :thumb do
-    process resize_to_fill: [20, 20]
-  end
-end
-```
-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:
-```erb
-<%= form_for @user, html: { multipart: true } do |f| %>
-  <p>
-    <label>My Avatar</label>
-    <%= f.file_field :avatar %>
-    <%= f.hidden_field :avatar_cache %>
-  </p>
-<% 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:
-```erb
-<%= form_for @user, html: { multipart: true } do |f| %>
-  <p>
-    <label>My Avatar</label>
-    <%= image_tag(@user.avatar_url) if @user.avatar? %>
-    <%= f.file_field :avatar %>
-    <%= f.hidden_field :avatar_cache %>
-  </p>
-<% 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.
-```erb
-<%= form_for @user, html: { multipart: true } do |f| %>
-  <p>
-    <label>My Avatar</label>
-    <%= image_tag(@user.avatar_url) if @user.avatar? %>
-    <%= f.file_field :avatar %>
-  </p>
-  <p>
-    <label>
-      <%= f.check_box :remove_avatar %>
-      Remove avatar
-    </label>
-  </p>
-<% end %>
-```
-If you want to remove the file manually, you can call <code>remove_avatar!</code>, then save the object.
-```erb
-@user.remove_avatar!
-@user.save
-#=> 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:
-```erb
-<%= form_for @user, html: { multipart: true } do |f| %>
-  <p>
-    <label>My Avatar URL:</label>
-    <%= image_tag(@user.avatar_url) if @user.avatar? %>
-    <%= f.text_field :remote_avatar_url %>
-  </p>
-<% 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:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def default_url(*args)
-    "/images/fallback/" + [version_name, "default.png"].compact.join('_')
-  end
-end
-```
-Or if you are using the Rails asset pipeline:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def default_url(*args)
-    ActionController::Base.helpers.asset_path("fallback/" + [version_name, "default.png"].compact.join('_'))
-  end
-end
-```
-## 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.
-```ruby
-instance = MyUploader.new
-instance.recreate_versions!(:thumb, :large)
-```
-Or on a mounted uploader:
-```ruby
-User.find_each do |user|
-  user.avatar.recreate_versions!
-end
-```
-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:
-```ruby
-User.find_each do |user|
-  user.avatar.recreate_versions! if user.avatar?
-end
-```
-## Configuring CarrierWave
-CarrierWave has a broad range of configuration options, which you can configure,
-both globally and on a per-uploader basis:
-```ruby
-CarrierWave.configure do |config|
-  config.permissions = 0666
-  config.directory_permissions = 0777
-  config.storage = :file
-end
-```
-Or alternatively:
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  permissions 0777
-end
-```
-If you're using Rails, create an initializer for this:
-	config/initializers/carrierwave.rb
-If you want CarrierWave to fail noisily in development, you can change these configs in your environment file:
-```ruby
-CarrierWave.configure do |config|
-  config.ignore_integrity_errors = false
-  config.ignore_processing_errors = false
-  config.ignore_download_errors = false
-end
-```
-## 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:
-```ruby
-if Rails.env.test? or Rails.env.cucumber?
-  CarrierWave.configure do |config|
-    config.storage = :file
-    config.enable_processing = false
-  end
-end
-```
-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:
-```ruby
-require 'carrierwave/test/matchers'
-describe MyUploader do
-  include CarrierWave::Test::Matchers
-  let(:user) { double('user') }
-  let(:uploader) { MyUploader.new(user, :avatar) }
-  before do
-    MyUploader.enable_processing = true
-    File.open(path_to_file) { |f| uploader.store!(f) }
-  end
-  after do
-    MyUploader.enable_processing = false
-    uploader.remove!
-  end
-  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)
-    end
-  end
-  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)
-    end
-  end
-  it "makes the image readable only to the owner and not executable" do
-    expect(uploader).to have_permissions(0600)
-  end
-  it "has the correct format" do
-    expect(uploader).to be_format('png')
-  end
-end
-```
-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:
-```ruby
-@uploader.thumb.enable_processing = true
-```
-## Fog
-If you want to use fog you must add in your CarrierWave initializer the
-following lines
-```ruby
-config.fog_provider = 'fog' # 'fog/aws' etc. Defaults to 'fog'
-config.fog_credentials = { ... } # Provider specific credentials
-```
-## Using Amazon S3
-[Fog AWS](http://github.com/fog/fog-aws) is used to support Amazon S3. Ensure you have it in your Gemfile:
-```ruby
-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:
-```ruby
-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:                  's3.example.com',             # optional, defaults to nil
-    endpoint:              'https://s3.example.com:8080' # optional, defaults to nil
-  }
-  config.fog_directory  = 'name_of_directory'                          # required
-  config.fog_public     = false                                        # optional, defaults to true
-  config.fog_attributes = { 'Cache-Control' => "max-age=#{365.day.to_i}" } # optional, defaults to {}
-end
-```
-In your uploader, set the storage to :fog
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  storage :fog
-end
-```
-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](http://github.com/fog/fog) is used to support Rackspace Cloud Files. Ensure you have it in your Gemfile:
-```ruby
-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:
-```ruby
-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'
-end
-```
-Using a UK-based account:
-```ruby
-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'
-end
-```
-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.
-```ruby
-config.asset_host = "http://c000000.cdn.rackspacecloud.com"
-```
-In your uploader, set the storage to :fog
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  storage :fog
-end
-```
-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](http://github.com/fog/fog-google) is used to support Google Storage for Developers. Ensure you have it in your Gemfile:
-```ruby
-gem "fog-google"
-gem "google-api-client", "< 0.9", ">= 0.6.2"
-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](https://github.com/fog/fog-google/blob/master/README.md) on how to get credentials.
-```ruby
-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'
-end
-```
-In your uploader, set the storage to :fog
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  storage :fog
-end
-```
-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:
-```ruby
-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:
-```ruby
-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](https://github.com/fog).
-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.
-```ruby
-CarrierWave.configure do |config|
-  config.asset_host = proc do |file|
-    identifier = # some logic
-    "http://#{identifier}.cdn.rackspacecloud.com"
-  end
-end
-```
-## 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:
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  include CarrierWave::RMagick
-end
-```
-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.
-```ruby
-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?
-  end
-end
-```
-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:
-https://github.com/minimagick/minimagick
-And the ImageMagick command line options for more for whats on offer:
-http://www.imagemagick.org/script/command-line-options.php
-Currently, the MiniMagick carrierwave processor provides exactly the same methods as
-for the RMagick processor.
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  include CarrierWave::MiniMagick
-  process resize_to_fill: [200, 200]
-end
-```
-## Migrating from Paperclip
-If you are using Paperclip, you can use the provided compatibility module:
-```ruby
-class AvatarUploader < CarrierWave::Uploader::Base
-  include CarrierWave::Compatibility::Paperclip
-end
-```
-See the documentation for `CarrierWave::Compatibility::Paperclip` for more
-details.
-Be sure to use mount_on to specify the correct column:
-```ruby
-mount_uploader :avatar, AvatarUploader, mount_on: :avatar_file_name
-```
-## I18n
-The Active Record validations use the Rails i18n framework. Add these keys to
-your translations file:
-```yaml
-errors:
-  messages:
-    carrierwave_processing_error: "Cannot resize image."
-    carrierwave_integrity_error: "Not an image."
-    carrierwave_download_error: "Couldn't download image."
-    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}"
-```
-## 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:
-```ruby
-class MyUploader < CarrierWave::Uploader::Base
-  def move_to_cache
-    true
-  end
-  def move_to_store
-    true
-  end
-end
-```
-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:
-```ruby
-class User
-  mount_uploader :avatar, AvatarUploader
-end
-```
-Will add these callbacks:
-```ruby
-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 ActiveRecord’s
-`skip_callback` method.
-```ruby
-class User
-  mount_uploader :avatar, AvatarUploader
-  skip_callback :commit, :after, :remove_previously_stored_avatar
-end
-```
-## Contributing to CarrierWave
-See [CONTRIBUTING.md](https://github.com/carrierwaveuploader/carrierwave/blob/master/CONTRIBUTING.md)
-## License
-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.
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.