I like CarrierWave. That being said, I don't like tying up app instances waiting for images to process.
This gem addresses that issue by disabling processing until a background process initiates it. It supports Delayed Job, Resque and Girl Friday.
There are currently two offerings for backgrounding upload tasks which are as follows;
This method stores the original file and does no processing or versioning. Optionally you can add a column to the database which will be set to nil when the background processing is complete.
This method does nothing to the file after it is cached which makes it super fast. It requires a column in the database which stores the cache location set by carrierwave. The drawback to using this method is the need for a central location to store the cached files. This leave heroku out. Heroku may deploy workers on separate servers from where your dyno cached the files. That being said, I only recommend using this method if you have full control over your temp storage directory.
In Rails, add the following your Gemfile:
In an initializer:
CarrierWave::Backgrounder.configure do |c| # :delayed_job, :girl_friday, :sidekiq, :qu, :resque, or :qc c.backend = :delayed_job end
In your CarrierWave uploader file:
class AvatarUploader < CarrierWave::Uploader::Base include ::CarrierWave::Backgrounder::Delay #etc... end
To use process_in_background
In your model:
mount_uploader :avatar, AvatarUploader process_in_background :avatar
Optionally you can add a column to the database which will be set to nil when the background processing is complete.
add_column :users, :avatar_processing, :boolean
To use store_in_background
In your model:
mount_uploader :avatar, AvatarUploader store_in_background :avatar
Add a column to the model you want to background which will store the temp file location:
add_column :users, :avatar_tmp, :string
If you need to process/store the upload immediately:
@user.process_<column>_upload = true
To overide the worker in cases where additional methods need to be called or you have app specific requirements, pass the worker class as the second argument:
process_in_background :avatar, MyAppsAwesomeProcessingWorker
Currently ActiveRecord is the default orm and I have not tested this with others but it should work by adding the following to your carrierwave initializer:
DataMapper::Model.send(:include, ::CarrierWave::Backgrounder::ORM::Base) # or Mongoid::Document::ClassMethods.send(:include, ::CarrierWave::Backgrounder::ORM::Base) # or Sequel::Model.send(:extend, ::CarrierWave::Backgrounder::ORM::Base)
Contributions are gladly accepted from those who use these orms.
Copyright (c) 2011 Larry Sprock
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.