day_planner 0.0.4 → 0.0.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +2 -2
- data/lib/day_planner/base.rb +2 -2
- 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: ff31def7cdc17c25def7b0076fdeddf8a8663512
|
4
|
+
data.tar.gz: 26e0dd03a52c87192c201dfce2b664c6284ea36d
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: f5c111fccf653d215791109f48fbea0c1a826512a431e093e46769c417dde0529fe060e61a95e3e85f9319f7c4d5893b819e22271ee06b10aa92123d9aef8041
|
7
|
+
data.tar.gz: 3389df345dc78fb28458e2fc0dbf2afe44a72d5d13ed1cbd7488436d6e006dc1339a23af53b248e3834323a7b4363b8199fe776b996a8d6654d64cddc8ce5313
|
data/README.md
CHANGED
@@ -24,7 +24,7 @@ If you're using Rails, it'll expect to find a file listing scheduled tasks in 'c
|
|
24
24
|
|
25
25
|
## Usage
|
26
26
|
|
27
|
-
Here's an example of a scheduled task, living in (app)/config/
|
27
|
+
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):
|
28
28
|
|
29
29
|
DayPlanner.schedule(every: 2.minutes) do
|
30
30
|
MyClass.my_class_method
|
@@ -34,7 +34,7 @@ Obviously you only get those cute little time methods in Rails; otherwise, pass
|
|
34
34
|
|
35
35
|
The tasks in the schedule will each be performed on startup and then thereafter according to their stated intervals.
|
36
36
|
|
37
|
-
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
|
37
|
+
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.
|
38
38
|
|
39
39
|
By default, DayPlanner checks for tasks to be performed once per minute. You have the power to change this:
|
40
40
|
|
data/lib/day_planner/base.rb
CHANGED
data/lib/day_planner/version.rb
CHANGED