delayed_paperclip 0.5.0 → 0.5.1

data/README.textile

@@ -1,35 +1,39 @@
 h1. Delayed::Paperclip
 
-Delayed_paperclip lets you process your "Paperclip":http://github.com/thoughtbot/paperclip attachments in a background task with "delayed_job":http://github.com/tobi/delayed_job.
-
-This is a fork that focuses on "Resque":http://github.com/defunkt/resque rather than Delayed::Job.  Everyone says that "they are both awesome":http://github.com/blog/542-introducing-resque, but, in my case, I'm already committed to using "Vanity":http://vanity.labnotes.org/ and, I'm no expert, but "redis and Vanity":http://groups.google.com/group/vanity-talk/browse_thread/thread/db6c106581a26c46/eccff9396bdb2fe8?show_docid=eccff9396bdb2fe8&fwc=1&pli=1# look like they're likely to go hand in hand for some time.  
+Delayed_paperclip lets you process your "Paperclip":http://github.com/thoughtbot/paperclip attachments in a background task with "delayed_job":http://github.com/tobi/delayed_job or "Resque":http://github.com/defunkt/resque.
 
 h2. Why?
 
-The "original author":http://github.com/jstorimer/delayed_paperclip says:
+The most common use case for Paperclip is to easily attach image files to ActiveRecord models. Most of the time these image files will have multiple styles and will need to be resized when they are created. This is usually a pretty "slow operation":http://www.jstorimer.com/ruby/2010/01/05/speep-up-your-paperclip-tests.html and should be handled in a background task. 
+
+I'm sure that everyone knows this, this gem just makes it easy to do.
 
-bq. The most common use case for Paperclip is to easily attach image files to ActiveRecord models. Most of the time these image files will have multiple styles and will need to be resized when they are created. This is usually a pretty "slow operation":http://www.jstorimer.com/ruby/2010/01/05/speep-up-your-paperclip-tests.html and should be handled in a background task. 
+h2. Installation
 
-bq. I'm sure that everyone knows this, this gem just makes it easy to do.
+Install the gem:
 
-I am also concerned with the "memory usage of ImageMagick":http://magick.imagemagick.org/script/architecture.php#cache and didn't want a few bad actors to be able to take down my site just by uploading some big pictures.
+<pre><code>sudo gem install delayed_paperclip</code></pre>
 
-h2. Installation
+Add it to your environment.rb:
 
-Not only do I have no idea how I would enable some kind of "two gems" approach, but also I don't know what the future of this project is, necessarily.  But it does work, and maybe you'll find it useful.
+<pre><code>config.gem 'delayed_paperclip'</code></pre>
+
+Or, even better, to your Gemfile:
+
+<pre><code>source "http://gemcutter.org"
+gem 'delayed_paperclip'
+</code></pre>
 
-Install as a rails plugin:
+Or install as a rails plugin:
 
-<pre><code>script/plugin install git://github.com/bigfleet/delayed_paperclip.git</code></pre>
+<pre><code>script/plugin install git://github.com/jstorimer/delayed_paperclip.git</code></pre>
 
 Dependencies:
 * Paperclip
-* resque
+* DJ or Resque
 
 h2. Usage
 
-Make sure that you have "Resque":http://github.com/defunkt/resque up and running.  The jobs will be dispatched to the <code>:paperclip</code> queue, so you can correctly dispatch your worker.  Configure resque and your worker exactly as you would otherwise.
-
 In your model:
 
 <pre><code>
@@ -42,6 +46,14 @@ In your model:
 
 Use your Paperclip attachment just like always in controllers and views.
 
+h3. Resque
+
+Make sure that you have "Resque":http://github.com/defunkt/resque up and running.  The jobs will be dispatched to the <code>:paperclip</code> queue, so you can correctly dispatch your worker.  Configure resque and your worker exactly as you would otherwise.
+
+h3. DJ
+
+Just make sure that you have DJ up and running.
+
 h2. What if I'm not using images?
 
 AFAIK this library should work no matter what kind of post-processing you are doing with Paperclip.

data/VERSION

@@ -1 +1 @@
-0.5.0
+0.5.1

data/delayed_paperclip.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{delayed_paperclip}
-  s.version = "0.5.0"
+  s.version = "0.5.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Jesse Storimer"]
-  s.date = %q{2010-02-09}
+  s.date = %q{2010-02-12}
   s.description = %q{Process your Paperclip attachments in the background with delayed_job.}
   s.email = %q{jesse@jstorimer.com}
   s.extra_rdoc_files = [

data/lib/delayed/paperclip.rb

@@ -21,7 +21,7 @@ module Delayed
         define_method "enqueue_job_for_#{name}" do
           if self.send("#{name}_changed?")
             if delayed_job?
-              Delayed::Job.enqueue DelayedPaperclipJob.new(read_attribute(:id), self.class.name, name.to_sym)
+              Delayed::Job.enqueue DelayedPaperclipJob.new(self.class.name, read_attribute(:id), name.to_sym)
             elsif resque?
               Resque.enqueue(ResquePaperclipJob, self.class.name, read_attribute(:id), name.to_sym)
             end

data/test/delayed_paperclip_test.rb

@@ -51,12 +51,13 @@ class DelayedPaperclipTest < Test::Unit::TestCase
   end
 
   def test_perform_job
+    @dummy.stubs(:image_changed?).returns(true)
     Paperclip::Attachment.any_instance.expects(:reprocess!)
 
     @dummy.save!
-    DelayedPaperclipJob.new(@dummy.class.name, @dummy.id, :image).perform
+    Delayed::Job.last.payload_object.perform
   end
-
+  
   def test_after_callback_is_functional
     @dummy_class.send(:define_method, :done_processing) { puts 'done' }
     @dummy_class.after_image_post_process :done_processing    

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: delayed_paperclip
 version: !ruby/object:Gem::Version 
-  version: 0.5.0
+  version: 0.5.1
 platform: ruby
 authors: 
 - Jesse Storimer
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-02-09 00:00:00 -05:00
+date: 2010-02-12 00:00:00 -05:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency