day_planner 0.0.12.1 → 0.0.13

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a18356accc7526285959f70146b9d69b4e3f7a73
-  data.tar.gz: cb79a13c6db5840e060f8edbe012a990aa0e5c96
+  metadata.gz: 2f22f16d1b49963c3290b1e6a8e91d3f4dfd1797
+  data.tar.gz: e6514798c238eab344078c3d2ca75fa418ea2a65
 SHA512:
-  metadata.gz: bbda3bb5e7ccd6c4b42cb6af1053e2f54eed73604c6be6be922d5fbc095cad5ba2c520820dc650da6cb83203d164881e9c8b77574aea73e063460c2657499c56
-  data.tar.gz: f1d489524a7729ce29c6d6845d9e9e54364abaacdcc9d451104ea6433b336e000c89b74310eeb03ab1dc87f65a5d4e554009867653acd078526f71d367c3229b
+  metadata.gz: d3b4905a664d1695fb2a6ffaa828da69822ef077f5537d50cf2f226d14f57b3a08a47e1b618aab07711edccf6edc5c8694f50fd244f8e648e3243c59b4e70d6f
+  data.tar.gz: 013cb5b39b8c68cb3ba8b283f63c1d8ab5ac19efb8adbf9f991bcd855e9bc34413686e073f87bf1232df13951fb69a3977f7e35d48c49f5f7f304fb097c702dc

data/README.md

@@ -14,11 +14,7 @@ Add this line to your application's Gemfile:
 
 And then execute:
 
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install day_planner
+    $ bundle install
 
 If you're using Rails, it'll expect to find a file listing scheduled tasks in 'config/scheduled_tasks.rb'. If you're not using Rails, do whatever makes you happy. Stick some scheduled tasks somewhere and make sure it's somewhere that runs when your application starts.
 
@@ -50,19 +46,7 @@ I have not tested it outside of Rails and it may not work at all but ideally I'd
 
 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. Remember that your interval is really the minimum possible time between instances of the task being performed, as it does not spawn a new thread for that purpose.
-
-By default, DayPlanner checks for tasks to be performed once per minute. You have the power to change this:
-
-    DayPlanner.interval = 5.seconds
-
-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 complain but not fail. The task 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.
+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. Remember that your interval is really the minimum possible time between instances of the task being performed, as it does not spawn a new thread for each task. (That seemed to cause problems with Heroku.)
 
 ### Other options
 
@@ -85,11 +69,32 @@ If you're using Rails, you can include environment in your options hash, setting
         # I run every hour, but only if you're using Rails and in production.
     end
 
+### Managing DayPlanner and tasks
+
+You can activate or deactivate DayPlanner with those respective methods. You can also check whether it's running with DayPlanner.status.
+
 To cancel a task, you can either call the task's "destroy" method, or call a class method on DayPlanner:
+
     DayPlanner.cancel(task)
 
 You can either pass a name, if you named the task, or the task object.
 
+#### DayPlanner.interval
+
+By default, DayPlanner checks for tasks to be performed once per minute. You have the power to change this:
+
+    DayPlanner.interval = 5.seconds
+
+Or, like
+
+    DayPlanner.interval = 5
+
+Since tasks are not run in separate threads (this seemed to be giving me database connection issues on Heroku), remember that the interval is basically a minimum possible period before it's performed again -- if a task takes time to run, keep that in mind (or spin off a new thread yourself in the task).
+
+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. The task 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. As long as you set your interval before DayPlanner is activated, you won't have to wait for it to cycle through an interval. If you alter this value while DayPlanner is already running, it won't take effect until the current interval ends.
+
 ## Contributing
 
 1. Fork it

data/lib/day_planner/base.rb

@@ -98,7 +98,7 @@ module DayPlanner
 		attr_reader :last_executed, :interval
 
 		def perform
-			if @environment.nil? || (defined?(Rails) && defined?(Rails.environment) && Rails.environment == @environment)
+			if @environment.nil? || (defined?(Rails) && defined?(Rails.env) && Rails.env == @environment)
 				@last_executed = Time.now
 
 				@task.call

data/lib/day_planner/version.rb

@@ -1,8 +1,8 @@
 module DayPlanner
 	MAJOR = 0
 	MINOR = 0
-	TINY  = 12
-	BUILD = 1
+	TINY  = 13
+	BUILD = nil
 
   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.12.1
+  version: 0.0.13
 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.3
+rubygems_version: 2.0.14
 signing_key: 
 specification_version: 4
 summary: Built to have a way to schedule tasks without running an extra process and