resque-scheduler 2.5.5 → 3.0.0
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of resque-scheduler might be problematic. Click here for more details.
- checksums.yaml +4 -4
- data/.gitignore +12 -6
- data/.rubocop.yml +18 -113
- data/.rubocop_todo.yml +29 -0
- data/.simplecov +3 -1
- data/.travis.yml +12 -4
- data/.vagrant-provision-as-vagrant.sh +15 -0
- data/.vagrant-provision.sh +23 -0
- data/.vagrant-skel/bash_profile +7 -0
- data/.vagrant-skel/bashrc +7 -0
- data/AUTHORS.md +5 -0
- data/Gemfile +1 -2
- data/HISTORY.md +18 -0
- data/README.md +39 -11
- data/ROADMAP.md +0 -6
- data/Rakefile +11 -19
- data/Vagrantfile +14 -0
- data/bin/resque-scheduler +2 -2
- data/examples/Rakefile +1 -1
- data/examples/config/initializers/resque-web.rb +2 -2
- data/examples/dynamic-scheduling/app/jobs/fix_schedules_job.rb +2 -4
- data/examples/dynamic-scheduling/app/jobs/send_email_job.rb +1 -1
- data/examples/dynamic-scheduling/app/models/user.rb +2 -2
- data/examples/dynamic-scheduling/lib/tasks/resque.rake +2 -2
- data/lib/resque-scheduler.rb +3 -1
- data/lib/resque/scheduler.rb +112 -168
- data/lib/resque/scheduler/cli.rb +144 -0
- data/lib/resque/scheduler/configuration.rb +73 -0
- data/lib/resque/scheduler/delaying_extensions.rb +278 -0
- data/lib/resque/scheduler/env.rb +61 -0
- data/lib/resque/scheduler/extension.rb +13 -0
- data/lib/resque/scheduler/lock.rb +2 -1
- data/lib/resque/scheduler/lock/base.rb +6 -2
- data/lib/resque/scheduler/lock/basic.rb +4 -5
- data/lib/resque/scheduler/lock/resilient.rb +30 -37
- data/lib/resque/scheduler/locking.rb +94 -0
- data/lib/resque/scheduler/logger_builder.rb +72 -0
- data/lib/resque/scheduler/plugin.rb +31 -0
- data/lib/resque/scheduler/scheduling_extensions.rb +150 -0
- data/lib/resque/scheduler/server.rb +246 -0
- data/lib/{resque_scheduler → resque/scheduler}/server/views/delayed.erb +2 -1
- data/lib/{resque_scheduler → resque/scheduler}/server/views/delayed_schedules.erb +0 -0
- data/lib/{resque_scheduler → resque/scheduler}/server/views/delayed_timestamp.erb +0 -0
- data/lib/{resque_scheduler → resque/scheduler}/server/views/requeue-params.erb +0 -0
- data/lib/{resque_scheduler → resque/scheduler}/server/views/scheduler.erb +16 -1
- data/lib/{resque_scheduler → resque/scheduler}/server/views/search.erb +2 -1
- data/lib/{resque_scheduler → resque/scheduler}/server/views/search_form.erb +0 -0
- data/lib/resque/scheduler/signal_handling.rb +40 -0
- data/lib/{resque_scheduler → resque/scheduler}/tasks.rb +3 -5
- data/lib/resque/scheduler/util.rb +41 -0
- data/lib/resque/scheduler/version.rb +7 -0
- data/resque-scheduler.gemspec +21 -19
- data/script/migrate_to_timestamps_set.rb +5 -3
- data/tasks/resque_scheduler.rake +1 -1
- data/test/cli_test.rb +26 -69
- data/test/delayed_queue_test.rb +262 -169
- data/test/env_test.rb +41 -0
- data/test/resque-web_test.rb +169 -48
- data/test/scheduler_args_test.rb +73 -41
- data/test/scheduler_hooks_test.rb +9 -8
- data/test/scheduler_locking_test.rb +55 -36
- data/test/scheduler_setup_test.rb +52 -15
- data/test/scheduler_task_test.rb +15 -10
- data/test/scheduler_test.rb +215 -114
- data/test/support/redis_instance.rb +32 -33
- data/test/test_helper.rb +33 -36
- data/test/util_test.rb +11 -0
- metadata +113 -57
- data/lib/resque/scheduler_locking.rb +0 -91
- data/lib/resque_scheduler.rb +0 -386
- data/lib/resque_scheduler/cli.rb +0 -160
- data/lib/resque_scheduler/logger_builder.rb +0 -72
- data/lib/resque_scheduler/plugin.rb +0 -28
- data/lib/resque_scheduler/server.rb +0 -183
- data/lib/resque_scheduler/util.rb +0 -34
- data/lib/resque_scheduler/version.rb +0 -5
- data/test/redis-test.conf +0 -108
data/test/redis-test.conf
DELETED
@@ -1,108 +0,0 @@
|
|
1
|
-
# Redis configuration file example
|
2
|
-
|
3
|
-
# By default Redis does not run as a daemon. Use 'yes' if you need it.
|
4
|
-
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
|
5
|
-
daemonize yes
|
6
|
-
|
7
|
-
# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
|
8
|
-
# You can specify a custom pid file location here.
|
9
|
-
pidfile ./test/redis-test.pid
|
10
|
-
|
11
|
-
# Accept connections on the specified port, default is 6379
|
12
|
-
port 9736
|
13
|
-
|
14
|
-
# If you want you can bind a single interface, if the bind option is not
|
15
|
-
# specified all the interfaces will listen for connections.
|
16
|
-
#
|
17
|
-
# bind 127.0.0.1
|
18
|
-
|
19
|
-
# Close the connection after a client is idle for N seconds (0 to disable)
|
20
|
-
timeout 300
|
21
|
-
|
22
|
-
# Save the DB on disk:
|
23
|
-
#
|
24
|
-
# save <seconds> <changes>
|
25
|
-
#
|
26
|
-
# Will save the DB if both the given number of seconds and the given
|
27
|
-
# number of write operations against the DB occurred.
|
28
|
-
#
|
29
|
-
# In the example below the behaviour will be to save:
|
30
|
-
# after 900 sec (15 min) if at least 1 key changed
|
31
|
-
# after 300 sec (5 min) if at least 10 keys changed
|
32
|
-
# after 60 sec if at least 10000 keys changed
|
33
|
-
save 900 1
|
34
|
-
save 300 10
|
35
|
-
save 60 10000
|
36
|
-
|
37
|
-
# The filename where to dump the DB
|
38
|
-
dbfilename dump.rdb
|
39
|
-
|
40
|
-
# For default save/load DB in/from the working directory
|
41
|
-
# Note that you must specify a directory not a file name.
|
42
|
-
dir ./test/
|
43
|
-
|
44
|
-
# Set server verbosity to 'debug'
|
45
|
-
# it can be one of:
|
46
|
-
# debug (a lot of information, useful for development/testing)
|
47
|
-
# notice (moderately verbose, what you want in production probably)
|
48
|
-
# warning (only very important / critical messages are logged)
|
49
|
-
loglevel debug
|
50
|
-
|
51
|
-
# Specify the log file name. Also 'stdout' can be used to force
|
52
|
-
# the demon to log on the standard output. Note that if you use standard
|
53
|
-
# output for logging but daemonize, logs will be sent to /dev/null
|
54
|
-
logfile stdout
|
55
|
-
|
56
|
-
# Set the number of databases. The default database is DB 0, you can select
|
57
|
-
# a different one on a per-connection basis using SELECT <dbid> where
|
58
|
-
# dbid is a number between 0 and 'databases'-1
|
59
|
-
databases 16
|
60
|
-
|
61
|
-
################################# REPLICATION #################################
|
62
|
-
|
63
|
-
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
|
64
|
-
# another Redis server. Note that the configuration is local to the slave
|
65
|
-
# so for example it is possible to configure the slave to save the DB with a
|
66
|
-
# different interval, or to listen to another port, and so on.
|
67
|
-
|
68
|
-
# slaveof <masterip> <masterport>
|
69
|
-
|
70
|
-
################################## SECURITY ###################################
|
71
|
-
|
72
|
-
# Require clients to issue AUTH <PASSWORD> before processing any other
|
73
|
-
# commands. This might be useful in environments in which you do not trust
|
74
|
-
# others with access to the host running redis-server.
|
75
|
-
#
|
76
|
-
# This should stay commented out for backward compatibility and because most
|
77
|
-
# people do not need auth (e.g. they run their own servers).
|
78
|
-
|
79
|
-
# requirepass foobared
|
80
|
-
|
81
|
-
################################### LIMITS ####################################
|
82
|
-
|
83
|
-
# Set the max number of connected clients at the same time. By default there
|
84
|
-
# is no limit, and it's up to the number of file descriptors the Redis process
|
85
|
-
# is able to open. The special value '0' means no limts.
|
86
|
-
# Once the limit is reached Redis will close all the new connections sending
|
87
|
-
# an error 'max number of clients reached'.
|
88
|
-
|
89
|
-
# maxclients 128
|
90
|
-
|
91
|
-
# Don't use more memory than the specified amount of bytes.
|
92
|
-
# When the memory limit is reached Redis will try to remove keys with an
|
93
|
-
# EXPIRE set. It will try to start freeing keys that are going to expire
|
94
|
-
# in little time and preserve keys with a longer time to live.
|
95
|
-
# Redis will also try to remove objects from free lists if possible.
|
96
|
-
#
|
97
|
-
# If all this fails, Redis will start to reply with errors to commands
|
98
|
-
# that will use more memory, like SET, LPUSH, and so on, and will continue
|
99
|
-
# to reply to most read-only commands like GET.
|
100
|
-
#
|
101
|
-
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
|
102
|
-
# 'state' server or cache, not as a real DB. When Redis is used as a real
|
103
|
-
# database the memory usage will grow over the weeks, it will be obvious if
|
104
|
-
# it is going to use too much memory in the long run, and you'll have the time
|
105
|
-
# to upgrade. With maxmemory after the limit is reached you'll start to get
|
106
|
-
# errors for write operations, and this may even lead to DB inconsistency.
|
107
|
-
|
108
|
-
# maxmemory <bytes>
|