forked from lantins/resque-lock-timeout
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathresque-lock-timeout.gemspec
32 lines (27 loc) · 1.29 KB
/
resque-lock-timeout.gemspec
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Gem::Specification.new do |s|
s.name = 'resque-lock-timeout'
s.version = '0.4.5'
s.date = Time.now.strftime('%Y-%m-%d')
s.summary = 'A Resque plugin adding locking, with optional timeout/deadlock handling to resque jobs.'
s.license = 'MIT'
s.homepage = 'http://github.com/lantins/resque-lock-timeout'
s.email = 'luke@lividpenguin.com'
s.authors = ['Luke Antins', 'Ryan Carver', 'Chris Wanstrath']
s.has_rdoc = false
s.files = %w(README.md Rakefile LICENSE HISTORY.md)
s.files += Dir.glob('lib/**/*')
s.files += Dir.glob('test/**/*')
s.add_dependency('resque', '~> 1.22')
s.add_development_dependency('rake', '~> 10.3')
s.add_development_dependency('minitest', '~> 5.2')
s.add_development_dependency('yard', '~> 0.8')
s.add_development_dependency('simplecov', '~> 0.7', '>= 0.7.1')
s.description = <<desc
A Resque plugin. Adds locking, with optional timeout/deadlock handling to
resque jobs.
Using a `lock_timeout` allows you to re-acquire the lock should your worker
fail, crash, or is otherwise unable to relase the lock.
i.e. Your server unexpectedly looses power. Very handy for jobs that are
recurring or may be retried.
desc
end