day_planner 0.1.0.pre5 → 0.1.0.pre5.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -1
- data/lib/day_planner/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 84ea53ef9ee61558d913d63d5b8e2fc7aad47946
|
4
|
+
data.tar.gz: bb3f02b7d0751832d57c33ac6b472bd29e566d21
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 8f60b4ccb2e55e27a23a0735101737f7c52d24bacfd606159948f009e06d55fb648fab19c6accfe76d3d402ea19c464cc4136d9afd6edf3db4e4509e4db29adb
|
7
|
+
data.tar.gz: 76137ccb8aeeb5c7b44f61ac3ff8f19b390d55f4bcea16908246f0766b03acc428ecfd381cab95927b458050b6bd6304986ec23157335c87e8d998bb54232f09
|
data/README.md
CHANGED
@@ -71,7 +71,7 @@ Since tasks are not run in separate threads (this seemed to be giving me databas
|
|
71
71
|
|
72
72
|
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.
|
73
73
|
|
74
|
-
Specify your preferred interval (and whatever other settings which may be implemented one day) in config/
|
74
|
+
Specify your preferred interval (and whatever other settings which may be implemented one day) in config/scheduled_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 to change the setting. If you alter this value while DayPlanner is already running, it won't take effect until the current interval ends.
|
75
75
|
|
76
76
|
## Contributing
|
77
77
|
|
data/lib/day_planner/version.rb
CHANGED