day_planner 0.0.3 → 0.0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8e3db46fdb6f0e4d44bbb8cf35cc3a79e5a70591
-  data.tar.gz: 67ed162a83dc83baa7715518d81744a0102d7d73
+  metadata.gz: ba232608de836dc7719d47a3e0f78cf666bf2959
+  data.tar.gz: 27f627cf08e43c49920dc264b08e68515bd57b49
 SHA512:
-  metadata.gz: 6499ba96a636101542b4099a3fa5827516756cc1112e7cde358ef854e3579d59954171b125758515ac7e8c41459f0bffc23fc32334b03f817fc8fc31d3b1eae8
-  data.tar.gz: 072b2e04e07eb1e63a68fff4246899416a6a3af2c1a4c9067899c1b0d72e8f1f12a899b753d7e22b612817cbaade3e7209301579f4cce39b7db1e5e608fd2c80
+  metadata.gz: c5b6e762927a4d64dc2b1787fc77af13c43a45cc70235a19d94e3523491b7eff1272dff13f1f795e4e3deffc3d409181f20cd06c268b212cfe399d05525f76c2
+  data.tar.gz: 08ab525349d6e9b54a840c6e86ddd95b0f6e380604fdc1dcb76de2ec2f0a2223d6eefd2494437f77cea215544e9a58570f314d1b4281e11452c0cb289d52a630

data/README.md

@@ -1,6 +1,6 @@
 # DayPlanner
 
-Day Planner is a simple tool to manage in-process execution of scheduled tasks. There are a lot of tools for running scheduled tasks outside the process ([Clockwork](http://rubygems.org/gems/clockwork) is probably what you're looking for if you want an elegant implementation of scheduled tasks outside the main process.)
+Day Planner is a simple tool to manage in-process execution of scheduled tasks. There are a lot of tools for running scheduled tasks outside the process ([Clockwork](http://rubygems.org/gems/clockwork) is probably what you're looking for if you want an elegant implementation of scheduled tasks outside the main process).
 
 I wrote this because I needed a simple, lightweight tool to schedule small, light tasks on an application running on Heroku, without the extra cost of a dedicated clock process to handle it, but executing more frequently than Heroku's free scheduler permits.
 
@@ -24,7 +24,7 @@ If you're using Rails, it'll expect to find a file listing scheduled tasks in 'c
 
 ## Usage
 
-Here's an example of a scheduled task:
+Here's an example of a scheduled task, living in (app)/config/day_planner_tasks.rb (this is the required/automatic location of the schedule file if you're using Rails):
 
     DayPlanner.schedule(every: 2.minutes) do
     	MyClass.my_class_method
@@ -34,6 +34,8 @@ Obviously you only get those cute little time methods in Rails; otherwise, pass
 
 The tasks in the schedule will each be performed on startup and then thereafter according to their stated intervals.
 
+I'm not doing a whole damn ton to protect you from tasks that throw errors, but there is a begin/rescue/end up in there at some point. I definitely am not protecting you from a process that just won't end or anything like that. Given that each task is run in its own thread, you have reasonable assurance that they are occuring at whatever interval you specify plus a very small amount of overhead.
+
 By default, DayPlanner checks for tasks to be performed once per minute. You have the power to change this:
 
     DayPlanner.interval = 5.seconds
@@ -42,9 +44,13 @@ Or, like
 
     DayPlanner.interval = 5
 
-Note that if you try to schedule a task with an interval shorter than DayPlanner's interval, it'll complain and fail. If you shorten DayPlanner's interval to less than that of one of its tasks, it'll probably also complain and fail. Use your best judgment.
+Note that if you try to schedule a task with an interval shorter than DayPlanner's interval, it'll complain and fail. If you shorten DayPlanner's interval to less than that of one of its tasks, it'll complain but not fail. It obviously will only run at scheduler thread's intervals. Use your best judgment.
+
+Specify your preferred interval (and whatever other goodies may be waiting in the pipeline) in config/day_planner_tasks.rb. Note that you probably won't manage to precede that first minute-long wait. I may default to a shorter value in the future. I dunno. Don't pressure me.
+
+### Non-Rails uses
 
-Specify these things in config/day_planner_tasks.rb. Note that you probably won't manage to precede that first minute-long wait. I may default to a shorter value in the future. I dunno.
+I sort of think it might work without Rails, keeping in mind the various aforementioned caveats? I'm not really sure. If it totally doesn't, I'd appreciate feedback.
 
 ## Contributing
 

data/lib/day_planner/version.rb

@@ -2,7 +2,7 @@ module DayPlanner
 	MAJOR = 0
 	MINOR = 0
 	TINY  = 3
-	BUILD = nil
+	BUILD = 1
 
   VERSION = [MAJOR, MINOR, TINY, BUILD].compact.join(".")
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: day_planner
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.3.1
 platform: ruby
 authors:
 - Damon Siefert
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.14
+rubygems_version: 2.0.3
 signing_key: 
 specification_version: 4
 summary: Built to have a way to schedule tasks without running an extra process and