torquebox-sidekiq-service 0.1.3 → 0.2.0
Sign up to get free protection for your applications and to get access to all the features.
- data/ChangeLog.md +15 -0
- data/VERSION +1 -1
- data/lib/torque_box/sidekiq_service.rb +3 -0
- data/torquebox-sidekiq-service.gemspec +5 -2
- metadata +22 -4
data/ChangeLog.md
CHANGED
@@ -1,3 +1,18 @@
|
|
1
|
+
0.2.0 (05/05/2013)
|
2
|
+
------------------
|
3
|
+
|
4
|
+
* Configured Celluloid to use TaskThreads instead of the default TaskFibers, as TaskThreads work better on JRuby.
|
5
|
+
|
6
|
+
0.1.3 (04/30/2013)
|
7
|
+
------------------
|
8
|
+
|
9
|
+
* Require 'celluloid/autostart' so its at_exit handler is registered, otherwise it'll leak threads when the service is stopped.
|
10
|
+
|
11
|
+
0.1.2 (04/30/2013)
|
12
|
+
------------------
|
13
|
+
|
14
|
+
* Added a definition for Sidekiq::Shutdown like Sidekiq's CLI does so things don't blow up when the class isn't available.
|
15
|
+
|
1
16
|
0.1.1 (03/28/2013)
|
2
17
|
------------------
|
3
18
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.
|
1
|
+
0.2.0
|
@@ -35,6 +35,9 @@ module TorqueBox
|
|
35
35
|
Sidekiq::Logging.logger = TorqueBox::Logger.new('sidekiq') if ENV.has_key?('TORQUEBOX_CONTEXT')
|
36
36
|
end
|
37
37
|
|
38
|
+
require 'celluloid'
|
39
|
+
Celluloid.task_class = Celluloid::TaskThread
|
40
|
+
|
38
41
|
require 'celluloid/autostart'
|
39
42
|
|
40
43
|
if Sidekiq.options.has_key?(:verbose)
|
@@ -5,11 +5,11 @@
|
|
5
5
|
|
6
6
|
Gem::Specification.new do |s|
|
7
7
|
s.name = "torquebox-sidekiq-service"
|
8
|
-
s.version = "0.
|
8
|
+
s.version = "0.2.0"
|
9
9
|
|
10
10
|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
|
11
11
|
s.authors = ["Kevin Menard"]
|
12
|
-
s.date = "2013-
|
12
|
+
s.date = "2013-05-06"
|
13
13
|
s.description = " The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor. This\n allows TorqueBox features only available in-container to be usable by all your Sidekiq workers. It has the added\n benefit of reducing memory overhead by running in a single JVM and allows for better optimization through JIT and\n better debugging & profiling through TorqueBox's runtime inspection facilities.\n"
|
14
14
|
s.email = "nirvdrum@gmail.com"
|
15
15
|
s.extra_rdoc_files = [
|
@@ -49,6 +49,7 @@ Gem::Specification.new do |s|
|
|
49
49
|
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
50
50
|
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
51
51
|
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
52
|
+
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
52
53
|
else
|
53
54
|
s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
|
54
55
|
s.add_dependency(%q<sidekiq>, [">= 0"])
|
@@ -57,6 +58,7 @@ Gem::Specification.new do |s|
|
|
57
58
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
58
59
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
59
60
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
61
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
60
62
|
end
|
61
63
|
else
|
62
64
|
s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
|
@@ -66,6 +68,7 @@ Gem::Specification.new do |s|
|
|
66
68
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
67
69
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
68
70
|
s.add_dependency(%q<jeweler>, [">= 0"])
|
71
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
69
72
|
end
|
70
73
|
end
|
71
74
|
|
metadata
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: torquebox-sidekiq-service
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.3
|
5
4
|
prerelease:
|
5
|
+
version: 0.2.0
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
8
8
|
- Kevin Menard
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2013-
|
12
|
+
date: 2013-05-06 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: torquebox-sidekiq-service
|
@@ -137,6 +137,24 @@ dependencies:
|
|
137
137
|
none: false
|
138
138
|
prerelease: false
|
139
139
|
type: :development
|
140
|
+
- !ruby/object:Gem::Dependency
|
141
|
+
name: jeweler
|
142
|
+
version_requirements: !ruby/object:Gem::Requirement
|
143
|
+
requirements:
|
144
|
+
- - ">="
|
145
|
+
- !ruby/object:Gem::Version
|
146
|
+
version: !binary |-
|
147
|
+
MA==
|
148
|
+
none: false
|
149
|
+
requirement: !ruby/object:Gem::Requirement
|
150
|
+
requirements:
|
151
|
+
- - ">="
|
152
|
+
- !ruby/object:Gem::Version
|
153
|
+
version: !binary |-
|
154
|
+
MA==
|
155
|
+
none: false
|
156
|
+
prerelease: false
|
157
|
+
type: :development
|
140
158
|
description: |2
|
141
159
|
The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor. This
|
142
160
|
allows TorqueBox features only available in-container to be usable by all your Sidekiq workers. It has the added
|
@@ -174,10 +192,10 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
174
192
|
requirements:
|
175
193
|
- - ">="
|
176
194
|
- !ruby/object:Gem::Version
|
177
|
-
segments:
|
178
|
-
- 0
|
179
195
|
version: !binary |-
|
180
196
|
MA==
|
197
|
+
segments:
|
198
|
+
- 0
|
181
199
|
hash: 2
|
182
200
|
none: false
|
183
201
|
required_rubygems_version: !ruby/object:Gem::Requirement
|