day_planner 0.1.0.pre5.1 → 0.1.0.pre6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 84ea53ef9ee61558d913d63d5b8e2fc7aad47946
-  data.tar.gz: bb3f02b7d0751832d57c33ac6b472bd29e566d21
+  metadata.gz: 8d544914bc41dc8680a5dcbdb16e25d057db5f7c
+  data.tar.gz: e44d7fbc3890aa8b653c7c364ad971f9a6169efa
 SHA512:
-  metadata.gz: 8f60b4ccb2e55e27a23a0735101737f7c52d24bacfd606159948f009e06d55fb648fab19c6accfe76d3d402ea19c464cc4136d9afd6edf3db4e4509e4db29adb
-  data.tar.gz: 76137ccb8aeeb5c7b44f61ac3ff8f19b390d55f4bcea16908246f0766b03acc428ecfd381cab95927b458050b6bd6304986ec23157335c87e8d998bb54232f09
+  metadata.gz: 164909dfe43a45024a76685cbb1788abdd92bebd4dbc3a96c861dd5604a4f03d445794d45b8cbb940e96d8f03d221356c77fb224c51619441ad220f95815f567
+  data.tar.gz: a94ef5790e6d5c9a702e91d0f4d9dec105067e3325118f4f11ebee918bb5a857259019df288c8f9fc8d29eada95849f18e1b65c3b5238bbf5c22483fba87cc77

data/PLANS.md

@@ -0,0 +1,25 @@
+## For future releases ##
+
+### Track tasks across application launch instances ###
+This is basically a gimme as long as we're already recording stuff in a database:
+* Delete only anonymous tasks on initialize, don't delete anything with a persistent name and interval
+** But do delete any task with an unfamiliar name or name, interval combo
+* Don't worry about task content changing. Fine, change it. We don't store that in a database anyway.
+* Don't reinitialize persistent events, just keep them on schedule. This helps especially if e.g. dealing with a pricy API -- why pull more often than needed?
+
+### Log each tasks's history ###
+HIGH PRIORITY: I want to be able to monitor the elaborate new scheduling algorithm appropriately. This needs to be optional, but it would be nice to have the ability to monitor at least how well the task adheres to the timeline.
+
+### Attempt some degree of control with multi-process instances ###
+Not sure exactly how to do this.
+* Store a record of the scheduler's execution status in a database? Then use that to avoid it being unnecessarily run in multiple threads?
+* Hell, even an optional "view scheduler status" page in the app. Why not?
+
+### Some degree of DB independence ###
+This needs to wait until we have the multi-process thing down.
+* Set a separate interval for updating the DB, and in between just use in-memory stuff?
+** This probably would need to be done on some sort of basis of strict multiples, i.e. every 6th tick, update the database. Make sure that we can be okay with circumstances in which the DB is not up to date. (Tasks might resume unnecessarily soon, etc., but shit, do I care?)
+* The value of this is when the interval is quite low, at which point both the DB usage and the time that the queries take starts dominating the scene
+
+### Other task scheduling techniques ###
+Something cronesque, but not so annoying. Maybe options like hourly, daily, weekly, accompanied (optionally) by at, or on. These would need different logic from our "every", try-to-stay-on-task style items.

data/lib/day_planner/engine.rb

@@ -5,12 +5,14 @@ module DayPlanner
 	class Railtie < Rails::Engine
 		isolate_namespace DayPlanner
 
-		unless $0 =~ /rake/ || defined?(::Rails::Console) || !defined?(Rails.env) || !Rails.env.production?
-			initializer "day_planner.activate", after: :finisher_hook do
-				puts "DayPlanner starting up"
-				DayPlanner.clear_tasks
-				require Rails.root.join('config', 'scheduled_tasks')
-				DayPlanner.activate
+		unless $0 =~ /rake/ !defined?(Rails.env) || !Rails.env.production?
+			unless defined?(::Rails::Console) || ENV['EXECUTE_SCHEDULED_TASKS_IN_CONSOLE']
+				initializer "day_planner.activate", after: :finisher_hook do
+					puts "DayPlanner starting up"
+					DayPlanner.clear_tasks
+					require Rails.root.join('config', 'scheduled_tasks')
+					DayPlanner.activate
+				end
 			end
 		end
 	end

data/lib/day_planner/version.rb

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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: day_planner
 version: !ruby/object:Gem::Version
-  version: 0.1.0.pre5.1
+  version: 0.1.0.pre6.1
 platform: ruby
 authors:
 - Damon Siefert
@@ -77,6 +77,7 @@ files:
 - Gemfile
 - LICENSE
 - LICENSE.txt
+- PLANS.md
 - README.md
 - Rakefile
 - app/models/day_planner/task.rb