tickwork 0.1.0 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 920921d051336381f10e80c3d7241af9d1bd6089
-  data.tar.gz: ea06aed69b17703630a7dfdca5abaf54b9bdf015
+  metadata.gz: 4aca4243b33cbafaffd6fd7c70e12e6be3d81712
+  data.tar.gz: 0123d0ea00910ce13404126d037fcdc99e96e5e7
 SHA512:
-  metadata.gz: 5098df50b53894be834e88af9a0c303c8a6ea2618a5a8814a373c9f92ecffb4c6e71de097031da046e519c08d9cfb43ef266e82c97c1e203ecdac92133d3dbe3
-  data.tar.gz: a611528f519bf38cc5e063e107c354138b71094a1d7755b062ea4085e1833a3f010a68d988a263ded0ef22a8fed8cfb09b860881618022077c5e9cf4c7a6ca12
+  metadata.gz: 83369aefb73bfbd687c5455a956aeca132b23cd7aa8c087221070845ecade4629a2ea36d6513d1b6bb2836e9f70cde371dfc6a9198b1fd6cfca4f457437c3c51
+  data.tar.gz: 00b082f6478611419956844efc59ffa488d7ebd826bf7940a565b616373f0048ddc6b1e734a4e8bc383a03e4c11a777be88d31fafe01ff25bbde8dab9e165c9c

data/.gitignore

@@ -5,3 +5,4 @@ Gemfile.lock
 *.swo
 *.swp
 *.gem
+gem

data/.travis.yml

@@ -1,13 +1 @@
 language: ruby
-sudo: false
-cache: bundler
-rvm:
-  - 1.9.3
-  - 2.0.0
-  - 2.1
-  - 2.2
-  - jruby-19mode
-  - # rbx-2.2.7
-gemfile:
-  - gemfiles/activesupport3.gemfile
-  - gemfiles/activesupport4.gemfile

data/README.md

@@ -7,10 +7,16 @@ This started as a stripped down version of [clockwork](https://github.com/tomyka
 
 Tickwork provides a familiar and compatible config file for scheduled jobs, but instead of it being driven by a background process, it relies on regular calls to `Tickwork.run`. `Tickwork.run` efectively ticks the clock forward from the last time it was called scheduling jobs as it goes. By tuning the paramters below, you can call `Tickwork.run` as little or as often as you like. 
 
-Tickwork keeps track of time using a datastore. Right now, nothing is supported. 
+Tickwork keeps track of time using a datastore. This is compatible with `ActiveSupport::Cache::Store` so should be compatible with most cache stores out there. It is important the cache be distributed (so not `ActiveSupport::Cache::Store`). [AWS_Tickwork](https://github.com/softwaregravy/aws_tickwork) contains an example of an `ActiveRecord` implementation.
 
 Note that clockwork allowed schedules to be dynamically set via the database. This functionality does not exist in Tickwork.
 
+Possible Combinations
+-----------------------
+
+This was originally built with the idea of using [Cloudwatch Events](https://aws.amazon.com/blogs/aws/new-cloudwatch-events-track-and-respond-to-changes-to-your-aws-resources/) to power time. An implementation doing that is here: [AWS_Tickwork](https://github.com/softwaregravy/aws_tickwork). Another option would be [Heroku Scheduler](https://devcenter.heroku.com/articles/scheduler). I'm sure there are many more options out there.
+
+
 Quickstart
 ----------
 
@@ -19,6 +25,10 @@ Create tick.rb:
 ```ruby
 require 'tickwork'
 module Tickwork
+  configure do |config|
+    # See DataStore below
+    config[:data_store] = MyDataStore
+  end
   handler do |job|
     puts "Running #{job}"
   end
@@ -36,6 +46,8 @@ module Tickwork
 end
 ```
 
+Note, this needs to be global to access the config whenever you run Tickwork. If you're on rails, this should be an initializer. 
+
 If you need to load your entire environment for your jobs, simply add:
 
 ```ruby

data/lib/tickwork/manager.rb

@@ -22,6 +22,9 @@ module Tickwork
 
     def configure
       yield(config)
+      [:max_threads, :tick_size, :max_ticks, :max_catchup].each do |int_config_key|
+        config[int_config_key] = config[int_config_key].to_i
+      end
       if config[:sleep_timeout]
         config[:logger].warn 'INCORRECT USAGE: sleep_timeout is not used'
         if config[:sleep_timeout] < 1

data/test/manager_test.rb

@@ -162,6 +162,21 @@ end
     assert_equal 'superhero', @manager.config[:namespace]
   end
 
+  it "should be configurable and guard for string numbers" do
+    logger = NullLogger.new
+    @manager.configure do |config|
+      config[:max_threads] = "20"
+      config[:max_ticks] = "21"
+      config[:tick_size] = "59"
+      config[:max_catchup] = "3000"
+    end
+
+    assert_equal 20, @manager.config[:max_threads]
+    assert_equal 21, @manager.config[:max_ticks]
+    assert_equal 59, @manager.config[:tick_size]
+    assert_equal 3000, @manager.config[:max_catchup]
+  end
+
   it "configuration should have reasonable defaults" do
     @manager = Tickwork::Manager.new
     assert @manager.config[:logger].is_a?(Logger)

data/tickworkwork.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = "tickwork"
-  s.version = "0.1.0"
+  s.version = "0.9.0"
 
   s.authors = ["John Hinnegan"]
   s.license = 'MIT'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tickwork
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.9.0
 platform: ruby
 authors:
 - John Hinnegan
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-05-10 00:00:00.000000000 Z
+date: 2016-05-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: tzinfo