day_planner 0.0.4 → 0.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 087bf6c25abf28aae91daf4a2cc5588124c39ec0
-  data.tar.gz: ab0a8bd20205d887eed7284d2fb0525ec3f5acb6
+  metadata.gz: ff31def7cdc17c25def7b0076fdeddf8a8663512
+  data.tar.gz: 26e0dd03a52c87192c201dfce2b664c6284ea36d
 SHA512:
-  metadata.gz: 146334ddc8585204defae81055d90a9887a85014551cde59ed15b10a80718e553cf4b676c559f99203fee1d9abbf5ceb172aa40c14a1abce43b3b8c0b45875a9
-  data.tar.gz: f2a6f37630a0c7209903ca18d201ba23666bcde53d44c9978c4aa7434c9a1d2bb408eef3e7143e9bcbce411c0c31b7c8f53909ff7f89fbd6d2b95a7b1da540a9
+  metadata.gz: f5c111fccf653d215791109f48fbea0c1a826512a431e093e46769c417dde0529fe060e61a95e3e85f9319f7c4d5893b819e22271ee06b10aa92123d9aef8041
+  data.tar.gz: 3389df345dc78fb28458e2fc0dbf2afe44a72d5d13ed1cbd7488436d6e006dc1339a23af53b248e3834323a7b4363b8199fe776b996a8d6654d64cddc8ce5313

data/README.md

@@ -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, living in (app)/config/day_planner_tasks.rb (this is the required/automatic location of the schedule file if you're using Rails):
+Here's an example of a scheduled task, living in (app)/config/scheduled_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,7 +34,7 @@ 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.
+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 some faint 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:
 

data/lib/day_planner/base.rb

@@ -117,6 +117,6 @@ module DayPlanner
 	end
 end
 
-DayPlanner.activate
+require File.expand_path('config/scheduled_tasks') if defined?(Rails)
 
-require File.expand_path('config/day_planner_tasks') if defined?(Rails)
+DayPlanner.activate

data/lib/day_planner/version.rb

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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: day_planner
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
 platform: ruby
 authors:
 - Damon Siefert