serially 0.1.3 → 0.2.0

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    M2ZlZTI1ZjYzZmYwMTBhZDQ5ZDZhM2U3MTMzYjVmYmQwYzUwZTdjMQ==
+    ZDI4ZDNhOGNmOWY5NzdmZDQ2ZmQ0MTk0YmRiMTcxZDVkZWIwNDg0Mw==
   data.tar.gz: !binary |-
-    YmIzNTJmZGZhMGY1ZGZhMzY5YmUzNTZjNmI3MDRkZTU1Zjg1ZmI5YQ==
+    ZGMwODc1M2I1NWU5ZWQ4NTcyODlmM2I5ZTg3ZDI4OTU3ZjdhZjY2Mg==
 SHA512:
   metadata.gz: !binary |-
-    YWZhYzgzMTlhY2FkMzdlMDAyMWMyYTQ1ZjIzYjhkOWZmYzE4MjZiYTRjNzRk
-    MWM2YjI5N2NiMjBmNTNmOTAwZGQxZDc4YTkxNWQ4NTg2YWM3NTFjY2YxNzcy
-    OTg1N2U0MDFjMDYwYzA1YTJhYTkxOTdiNTU0ZTIyYzBjOWQ0ZGM=
+    MTZiMjE0YzQwYTQxNzUyNWQwOThkMDc0MjA4OWU1MGM0YjllMzVjZjc1NjFk
+    Y2Q0MGI2MWMxYjFmY2RhNDI3MTYyNTIwZmE0M2NiMDU5NWY2M2QxMDdmYjFi
+    NTIzMTcyZmQzNjAzODAzMjFkNmQwZTJlMjEwYWUyZWNjZGU0OTA=
   data.tar.gz: !binary |-
-    NjhjMTM3NTMwNTRhODQ3NTcxYmFkOTE5MWVjODg4ZGRlZjc3OGUyYjY2MWRj
-    MjA2ZGYwNDMwYzRjM2MyOTlmZjg2Y2M0NGRlN2FlOTI0YzkwNmI5NDdmZjhm
-    MWVkOGI0Y2YxYTM3ZjRhNjcxNGIxMjVmNGM0ZTY1MTNlNjA4MjU=
+    MmFmZWYxM2M4ODYxODRjNTYzNTE0ZDI3ZDE4MmI4MDU4ZjQ2N2E1OTAyYWZm
+    N2JiMWEyZjExMmU2MjJmOGFhNzNkZmMzZGM3NjNjMWFjZTQ2NGUzMmUwYzRi
+    ZmEyYTZmMjE2YzI3MGZhZjgxNjA5MzBjNzg5ZDMxM2Y3MmFkOTY=

data/README.md

@@ -5,11 +5,15 @@
 
 Have you ever had a class that required a series of background tasks to run serially, strictly one after another? Than Serially is for you.
 Declare the tasks using a simple DSL in the order you want them to to run. Serially will wrap them in a single job, and schedule it using Resque
-in `serially` queue (the queue is customizable). The next task will start only if previous one finished successfully. All task runs are written to DB  and can be inspected (if
+in a queue you specify (or a default one). The next task will run only if previous one finished successfully. All task runs are written to DB and can be inspected (if
 your class is an ActiveRecord object).
 
 Check [this demo app][1] to see how Serially may be used in a Rails app.
 
+Note: Serially is under active development. If there is anything you miss in it, please let me know!
+
+Twitter: @mikepolis     Email: mike AT polischuk DOT net
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -67,7 +71,8 @@ class Post < ActiveRecord::Base
    end
 ```
 
-After creating a Post, you can run `post.serially.start!` to schedule your Post tasks to run serially. They will run one after the other in the scope of the same `Serially::Job`.
+After creating a Post, you can run `post.serially.start!` to schedule your Post tasks to run serially. They will run one after the other in the scope of the same `Serially::Job`
+in the default `serially` queue.
 An example run:
 ```ruby
 post1 = Post.create(title: 'Critique of Pure Reason', author: 'Immanuel Kant') #=> <Post id: 1, title: 'Critique of Pure Reason'...>

data/lib/serially/version.rb

@@ -1,3 +1,3 @@
 module Serially
-  VERSION = "0.1.3"
+  VERSION = "0.2.0"
 end

data/serially.gemspec

@@ -35,9 +35,9 @@ Gem::Specification.new do |spec|
 
   spec.description   = <<desc
 Have you ever had a class that required a series of background tasks to run serially, strictly one after another? Than Serially is for you.
-All background jobs are scheduled using resque and Serially makes sure that for every instance of your class, only one task runs at a time.
-Different instances of the same class do not interfere with each other and their tasks can run in parallel.
-Serially works for both plain ruby classes and ActiveRecord models. In case of the latter, all task runs results are written to serially_tasks table which you can interrogate pragmatically using Serially::TaskRun model.
+Declare the tasks using a simple DSL in the order you want them to to run. Serially will wrap them in a single job, and schedule it using Resque
+in a queue you specify (or a default one). The next task will run only if previous one finished successfully. All task runs are written to DB and can be inspected (if
+your class is an ActiveRecord object).
 desc
 
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: serially
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.2.0
 platform: ruby
 authors:
 - Mike Polischuk
@@ -167,15 +167,14 @@ dependencies:
 description: ! 'Have you ever had a class that required a series of background tasks
   to run serially, strictly one after another? Than Serially is for you.
 
-  All background jobs are scheduled using resque and Serially makes sure that for
-  every instance of your class, only one task runs at a time.
+  Declare the tasks using a simple DSL in the order you want them to to run. Serially
+  will wrap them in a single job, and schedule it using Resque
 
-  Different instances of the same class do not interfere with each other and their
-  tasks can run in parallel.
+  in a queue you specify (or a default one). The next task will run only if previous
+  one finished successfully. All task runs are written to DB and can be inspected
+  (if
 
-  Serially works for both plain ruby classes and ActiveRecord models. In case of the
-  latter, all task runs results are written to serially_tasks table which you can
-  interrogate pragmatically using Serially::TaskRun model.
+  your class is an ActiveRecord object).
 
 '
 email: