Image processing via MiniMagick for Refile
Switch branches/tags
Nothing to show
Clone or download
janko-m Bump image_processing dependency to "~> 1.1"
The 1.x versions have many useful improvements, such as automatic
thumbnail sharpening, removal of deprecated MiniMagick API (which means
less memory), removal of default "-regard-warnings", and raising a
helpful exception when attempting to convert a multi-layer image into a
single-layer format without specifying a page.
Latest commit 466e30c Apr 6, 2018
Failed to load latest commit information.
lib/refile Switch to ImageProcessing chainable API Mar 21, 2018
spec/refile Change #resize_to_limit to accept nil Mar 9, 2018
.gitignore Initial extraction May 12, 2015
Gemfile Switch to image_processing gem Oct 3, 2015
LICENSE.txt Add "resample" processing action Oct 25, 2016
Rakefile Add rake task for rspec May 12, 2015
refile-mini_magick.gemspec Bump image_processing dependency to "~> 1.1" Apr 5, 2018


Image processing for Refile using MiniMagick.


gem 'refile-mini_magick'

Note that the master branch switched to using the ImageProcessing gem, which actively fixes the bugs reported on this repo, so it's recommended to pull refile-mini_magick from master:

gem 'refile-mini_magick', github: 'refile/refile-mini_magick'


The following processing helpers are provided for Refile:

  • /attachments/:token/:backend_name**/convert/jpg**/:id
  • /attachments/:token/:backend_name**/limit/500/500**/:id
  • /attachments/:token/:backend_name**/fit/500/500**/:id
  • /attachments/:token/:backend_name**/fill/500/500**/:id
  • /attachments/:token/:backend_name**/pad/500/500**/:id
  • /attachments/:token/:backend_name**/resample/500/500**/:id

Refile::MiniMagick internally delegates to ImageProcessing dependency gem, so you can read documentation about these processing actions on that repository.


  1. Fork it ( )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request