torquebox-sidekiq-service 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- data/Gemfile +14 -0
- data/LICENSE.txt +201 -0
- data/README.md +92 -0
- data/Rakefile +39 -0
- data/VERSION +1 -0
- data/lib/torque_box/sidekiq_service.rb +44 -0
- data/lib/torquebox-sidekiq-service.rb +10 -0
- data/test/helper.rb +12 -0
- data/test/sidekiq_service_test.rb +35 -0
- data/torquebox-sidekiq-service.gemspec +58 -0
- metadata +138 -0
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,92 @@
|
|
1
|
+
TorqueBox Sidekiq Service
|
2
|
+
=========================
|
3
|
+
|
4
|
+
This library provides a TorqueBox service for running Sidekiq inside the TorqueBox application server. It replaces the
|
5
|
+
Sidekiq CLI client typically used to start up TorqueBox.
|
6
|
+
|
7
|
+
Rationale
|
8
|
+
---------
|
9
|
+
|
10
|
+
The TorqueBox application server has a lot of features that are only accessible by running within the container. E.g.,
|
11
|
+
if your application uses the TorqueBox cache provider you cannot access that cache from an external process, like a
|
12
|
+
traditional Sidekiq setup. This can be confusing as something as benign as `Rails.cache` can have different values in
|
13
|
+
the same environment depending on how the code was invoked.
|
14
|
+
|
15
|
+
There are several other reasons why a TorqueBox service may make sense for you:
|
16
|
+
|
17
|
+
* Reduced memory consumption, as you'll only be using one JVM
|
18
|
+
* High availability, as TorqueBox can move a singleton service to any other node in a cluster
|
19
|
+
* Simpler process management, as Sidekiq will start as part of your normal application deploy
|
20
|
+
** No need for monit or similar tools in production
|
21
|
+
** No need for foreman or similar tools in development
|
22
|
+
* Easier to debug & profile by way of TorqueBox's debugging and profiling capabilities
|
23
|
+
* Better opportunity for JVM JIT optimization
|
24
|
+
|
25
|
+
Of course, for every item that I think is a pro, someone else may think is a con. Depending on perspective, some flaws
|
26
|
+
with this approach are:
|
27
|
+
|
28
|
+
* Not maintained by Sidekiq
|
29
|
+
* If the TorqueBox process dies Sidekiq goes with it
|
30
|
+
* Harder to measure just Sidekiq's memory footprint
|
31
|
+
* May no longer be able to deploy front-end independently of back-end (not strictly true since you can deploy multiple apps)
|
32
|
+
|
33
|
+
|
34
|
+
Usage
|
35
|
+
-----
|
36
|
+
|
37
|
+
If you want to run multiple Sidekiq processors in the same app, you'll need to use a bounded pool for the services runtime.
|
38
|
+
|
39
|
+
E.g., if you want to run two processors, with no other services, your torquebox.yml will need to have something like:
|
40
|
+
|
41
|
+
<pre>
|
42
|
+
pooling:
|
43
|
+
services:
|
44
|
+
type: bounded
|
45
|
+
min: 2
|
46
|
+
max: 2
|
47
|
+
</pre>
|
48
|
+
|
49
|
+
Then your service configuration would look like:
|
50
|
+
|
51
|
+
<pre>
|
52
|
+
services:
|
53
|
+
background-default:
|
54
|
+
service: TorqueBox::SidekiqService
|
55
|
+
config:
|
56
|
+
queues: ['default']
|
57
|
+
index: 0
|
58
|
+
concurrency: 50
|
59
|
+
|
60
|
+
background-deletes:
|
61
|
+
service: TorqueBox::SidekiqService
|
62
|
+
config:
|
63
|
+
queues: ['deletes']
|
64
|
+
index: 1
|
65
|
+
concurrency: 50
|
66
|
+
</pre>
|
67
|
+
|
68
|
+
By default, services are [singletons](http://torquebox.org/documentation/2.3.0/services.html#ha-singleton-services) in
|
69
|
+
TorqueBox, meaning they will run on only one node in the cluster. If that node ever goes down, the service will be
|
70
|
+
started on another available node. Alternatively, you can run a Sidekiq processor on all nodes by disabling the
|
71
|
+
singleton setting, like so:
|
72
|
+
|
73
|
+
<pre>
|
74
|
+
services:
|
75
|
+
background-default:
|
76
|
+
service: TorqueBox::SidekiqService
|
77
|
+
singleton: false
|
78
|
+
config:
|
79
|
+
queues: ['default']
|
80
|
+
index: 0
|
81
|
+
concurrency: 50
|
82
|
+
</pre>
|
83
|
+
|
84
|
+
|
85
|
+
Notes
|
86
|
+
-----
|
87
|
+
|
88
|
+
The torquebox-sidekiq-service must be loaded before you configure any Sidekiq server middleware. If it isn't loaded,
|
89
|
+
Sidekiq assumes your runtime environment is only as a client and will then ignore any server middleware configuration.
|
90
|
+
It'll then go on to use its default server middleware, which can lead to some confusing results. If you're on Rails,
|
91
|
+
everything in your Gemfile will be loaded by default so you won't have anything else to do. Otherwise, make sure you
|
92
|
+
require the library.
|
data/Rakefile
ADDED
@@ -0,0 +1,39 @@
|
|
1
|
+
# encoding: utf-8
|
2
|
+
|
3
|
+
require 'rubygems'
|
4
|
+
require 'bundler'
|
5
|
+
begin
|
6
|
+
Bundler.setup(:default, :development)
|
7
|
+
rescue Bundler::BundlerError => e
|
8
|
+
$stderr.puts e.message
|
9
|
+
$stderr.puts "Run `bundle install` to install missing gems"
|
10
|
+
exit e.status_code
|
11
|
+
end
|
12
|
+
require 'rake'
|
13
|
+
|
14
|
+
require 'jeweler'
|
15
|
+
Jeweler::Tasks.new do |gem|
|
16
|
+
# gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
|
17
|
+
gem.name = "torquebox-sidekiq-service"
|
18
|
+
gem.homepage = "http://github.com/mogotest/torquebox-sidekiq-service"
|
19
|
+
gem.license = "ASLv2"
|
20
|
+
gem.summary = 'A TorqueBox service for running Sidekiq in the TorqueBox application server.'
|
21
|
+
gem.description = <<-DESC
|
22
|
+
The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor. This
|
23
|
+
allows TorqueBox features only available in-container to be usable by all your Sidekiq workers. It has the added
|
24
|
+
benefit of reducing memory overhead by running in a single JVM and allows for better optimization through JIT and
|
25
|
+
better debugging & profiling through TorqueBox's runtime inspection facilities.
|
26
|
+
DESC
|
27
|
+
gem.email = "nirvdrum@gmail.com"
|
28
|
+
gem.authors = ["Kevin Menard"]
|
29
|
+
end
|
30
|
+
Jeweler::RubygemsDotOrgTasks.new
|
31
|
+
|
32
|
+
require 'rake/testtask'
|
33
|
+
Rake::TestTask.new(:test) do |test|
|
34
|
+
test.libs << 'lib' << 'test'
|
35
|
+
test.pattern = 'test/**/*_test.rb'
|
36
|
+
test.verbose = true
|
37
|
+
end
|
38
|
+
|
39
|
+
task :default => :test
|
data/VERSION
ADDED
@@ -0,0 +1 @@
|
|
1
|
+
0.1.0
|
@@ -0,0 +1,44 @@
|
|
1
|
+
module TorqueBox
|
2
|
+
class SidekiqService
|
3
|
+
attr_accessor :config, :launcher
|
4
|
+
|
5
|
+
CONFIG_OPTIONS_TO_STRIP = [:config_file, :daemon, :environment, :pidfile, :require, :tag]
|
6
|
+
|
7
|
+
def initialize(opts = {})
|
8
|
+
@config = opts.symbolize_keys.reject { |k, _| CONFIG_OPTIONS_TO_STRIP.include?(k) }
|
9
|
+
end
|
10
|
+
|
11
|
+
def start
|
12
|
+
Thread.new { run }
|
13
|
+
end
|
14
|
+
|
15
|
+
def stop
|
16
|
+
launcher.stop
|
17
|
+
end
|
18
|
+
|
19
|
+
def run
|
20
|
+
Sidekiq.options.merge!(config)
|
21
|
+
Sidekiq.options[:queues] << 'default' if Sidekiq.options[:queues].empty?
|
22
|
+
|
23
|
+
if Sidekiq.options.has_key?(:logfile)
|
24
|
+
Sidekiq::Logging.initialize_logger(Sidekiq.options[:logfile])
|
25
|
+
else
|
26
|
+
Sidekiq::Logging.logger = TorqueBox::Logger.new('sidekiq') if ENV.has_key?('TORQUEBOX_CONTEXT')
|
27
|
+
end
|
28
|
+
|
29
|
+
require 'celluloid'
|
30
|
+
|
31
|
+
if Sidekiq.options.has_key?(:verbose)
|
32
|
+
Sidekiq.logger.level = Logger::DEBUG
|
33
|
+
Celluloid.logger = Sidekiq.logger
|
34
|
+
end
|
35
|
+
|
36
|
+
require 'sidekiq/manager'
|
37
|
+
require 'sidekiq/scheduled'
|
38
|
+
require 'sidekiq/launcher'
|
39
|
+
@launcher = Sidekiq::Launcher.new(Sidekiq.options)
|
40
|
+
|
41
|
+
launcher.run
|
42
|
+
end
|
43
|
+
end
|
44
|
+
end
|
@@ -0,0 +1,10 @@
|
|
1
|
+
# This is needed to make Sidekiq think it's working in a server capacity.
|
2
|
+
module Sidekiq
|
3
|
+
class CLI
|
4
|
+
end
|
5
|
+
end
|
6
|
+
|
7
|
+
# Sidekiq requires its processor to be available if configuring server middleware.
|
8
|
+
require 'sidekiq/processor'
|
9
|
+
|
10
|
+
require 'torque_box/sidekiq_service'
|
data/test/helper.rb
ADDED
@@ -0,0 +1,35 @@
|
|
1
|
+
require 'helper'
|
2
|
+
|
3
|
+
class SidekiqServiceTest < MiniTest::Unit::TestCase
|
4
|
+
describe 'configuration' do
|
5
|
+
it 'should remove the daemon config option' do
|
6
|
+
service = TorqueBox::SidekiqService.new(daemon: true)
|
7
|
+
assert !service.config.has_key?(:daemon)
|
8
|
+
end
|
9
|
+
|
10
|
+
it 'should remove the environment config option' do
|
11
|
+
service = TorqueBox::SidekiqService.new(environment: 'production')
|
12
|
+
assert !service.config.has_key?(:environment)
|
13
|
+
end
|
14
|
+
|
15
|
+
it 'should remove the tag config option' do
|
16
|
+
service = TorqueBox::SidekiqService.new(tag: 'my-tag')
|
17
|
+
assert !service.config.has_key?(:tag)
|
18
|
+
end
|
19
|
+
|
20
|
+
it 'should remove the require config option' do
|
21
|
+
service = TorqueBox::SidekiqService.new(require: './lib')
|
22
|
+
assert !service.config.has_key?(:require)
|
23
|
+
end
|
24
|
+
|
25
|
+
it 'should remove the config_file config option' do
|
26
|
+
service = TorqueBox::SidekiqService.new(config_file: './config/sidekiq.yml')
|
27
|
+
assert !service.config.has_key?(:config_file)
|
28
|
+
end
|
29
|
+
|
30
|
+
it 'should remove the pidfile config option' do
|
31
|
+
service = TorqueBox::SidekiqService.new(pidfile: './tmp/sidekiq.pid')
|
32
|
+
assert !service.config.has_key?(:pidfile)
|
33
|
+
end
|
34
|
+
end
|
35
|
+
end
|
@@ -0,0 +1,58 @@
|
|
1
|
+
# Generated by jeweler
|
2
|
+
# DO NOT EDIT THIS FILE DIRECTLY
|
3
|
+
# Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
|
4
|
+
# -*- encoding: utf-8 -*-
|
5
|
+
|
6
|
+
Gem::Specification.new do |s|
|
7
|
+
s.name = "torquebox-sidekiq-service"
|
8
|
+
s.version = "0.1.0"
|
9
|
+
|
10
|
+
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
|
11
|
+
s.authors = ["Kevin Menard"]
|
12
|
+
s.date = "2013-03-14"
|
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
|
+
s.email = "nirvdrum@gmail.com"
|
15
|
+
s.extra_rdoc_files = [
|
16
|
+
"LICENSE.txt",
|
17
|
+
"README.md"
|
18
|
+
]
|
19
|
+
s.files = [
|
20
|
+
"Gemfile",
|
21
|
+
"LICENSE.txt",
|
22
|
+
"README.md",
|
23
|
+
"Rakefile",
|
24
|
+
"VERSION",
|
25
|
+
"lib/torque_box/sidekiq_service.rb",
|
26
|
+
"lib/torquebox-sidekiq-service.rb",
|
27
|
+
"test/helper.rb",
|
28
|
+
"test/sidekiq_service_test.rb",
|
29
|
+
"torquebox-sidekiq-service.gemspec"
|
30
|
+
]
|
31
|
+
s.homepage = "http://github.com/mogotest/torquebox-sidekiq-service"
|
32
|
+
s.licenses = ["ASLv2"]
|
33
|
+
s.require_paths = ["lib"]
|
34
|
+
s.rubygems_version = "1.8.24"
|
35
|
+
s.summary = "A TorqueBox service for running Sidekiq in the TorqueBox application server."
|
36
|
+
|
37
|
+
if s.respond_to? :specification_version then
|
38
|
+
s.specification_version = 3
|
39
|
+
|
40
|
+
if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
|
41
|
+
s.add_runtime_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
|
42
|
+
s.add_runtime_dependency(%q<sidekiq>, [">= 0"])
|
43
|
+
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
44
|
+
s.add_development_dependency(%q<jeweler>, [">= 0"])
|
45
|
+
else
|
46
|
+
s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
|
47
|
+
s.add_dependency(%q<sidekiq>, [">= 0"])
|
48
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
49
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
50
|
+
end
|
51
|
+
else
|
52
|
+
s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
|
53
|
+
s.add_dependency(%q<sidekiq>, [">= 0"])
|
54
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
55
|
+
s.add_dependency(%q<jeweler>, [">= 0"])
|
56
|
+
end
|
57
|
+
end
|
58
|
+
|
metadata
ADDED
@@ -0,0 +1,138 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: torquebox-sidekiq-service
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
prerelease:
|
5
|
+
version: 0.1.0
|
6
|
+
platform: ruby
|
7
|
+
authors:
|
8
|
+
- Kevin Menard
|
9
|
+
autorequire:
|
10
|
+
bindir: bin
|
11
|
+
cert_chain: []
|
12
|
+
date: 2013-03-14 00:00:00.000000000 Z
|
13
|
+
dependencies:
|
14
|
+
- !ruby/object:Gem::Dependency
|
15
|
+
name: torquebox-sidekiq-service
|
16
|
+
version_requirements: !ruby/object:Gem::Requirement
|
17
|
+
requirements:
|
18
|
+
- - ">="
|
19
|
+
- !ruby/object:Gem::Version
|
20
|
+
version: !binary |-
|
21
|
+
MA==
|
22
|
+
none: false
|
23
|
+
requirement: !ruby/object:Gem::Requirement
|
24
|
+
requirements:
|
25
|
+
- - ">="
|
26
|
+
- !ruby/object:Gem::Version
|
27
|
+
version: !binary |-
|
28
|
+
MA==
|
29
|
+
none: false
|
30
|
+
prerelease: false
|
31
|
+
type: :runtime
|
32
|
+
- !ruby/object:Gem::Dependency
|
33
|
+
name: sidekiq
|
34
|
+
version_requirements: !ruby/object:Gem::Requirement
|
35
|
+
requirements:
|
36
|
+
- - ">="
|
37
|
+
- !ruby/object:Gem::Version
|
38
|
+
version: !binary |-
|
39
|
+
MA==
|
40
|
+
none: false
|
41
|
+
requirement: !ruby/object:Gem::Requirement
|
42
|
+
requirements:
|
43
|
+
- - ">="
|
44
|
+
- !ruby/object:Gem::Version
|
45
|
+
version: !binary |-
|
46
|
+
MA==
|
47
|
+
none: false
|
48
|
+
prerelease: false
|
49
|
+
type: :runtime
|
50
|
+
- !ruby/object:Gem::Dependency
|
51
|
+
name: jeweler
|
52
|
+
version_requirements: !ruby/object:Gem::Requirement
|
53
|
+
requirements:
|
54
|
+
- - ">="
|
55
|
+
- !ruby/object:Gem::Version
|
56
|
+
version: !binary |-
|
57
|
+
MA==
|
58
|
+
none: false
|
59
|
+
requirement: !ruby/object:Gem::Requirement
|
60
|
+
requirements:
|
61
|
+
- - ">="
|
62
|
+
- !ruby/object:Gem::Version
|
63
|
+
version: !binary |-
|
64
|
+
MA==
|
65
|
+
none: false
|
66
|
+
prerelease: false
|
67
|
+
type: :development
|
68
|
+
- !ruby/object:Gem::Dependency
|
69
|
+
name: jeweler
|
70
|
+
version_requirements: !ruby/object:Gem::Requirement
|
71
|
+
requirements:
|
72
|
+
- - ">="
|
73
|
+
- !ruby/object:Gem::Version
|
74
|
+
version: !binary |-
|
75
|
+
MA==
|
76
|
+
none: false
|
77
|
+
requirement: !ruby/object:Gem::Requirement
|
78
|
+
requirements:
|
79
|
+
- - ">="
|
80
|
+
- !ruby/object:Gem::Version
|
81
|
+
version: !binary |-
|
82
|
+
MA==
|
83
|
+
none: false
|
84
|
+
prerelease: false
|
85
|
+
type: :development
|
86
|
+
description: |2
|
87
|
+
The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor. This
|
88
|
+
allows TorqueBox features only available in-container to be usable by all your Sidekiq workers. It has the added
|
89
|
+
benefit of reducing memory overhead by running in a single JVM and allows for better optimization through JIT and
|
90
|
+
better debugging & profiling through TorqueBox's runtime inspection facilities.
|
91
|
+
email: nirvdrum@gmail.com
|
92
|
+
executables: []
|
93
|
+
extensions: []
|
94
|
+
extra_rdoc_files:
|
95
|
+
- LICENSE.txt
|
96
|
+
- README.md
|
97
|
+
files:
|
98
|
+
- Gemfile
|
99
|
+
- LICENSE.txt
|
100
|
+
- README.md
|
101
|
+
- Rakefile
|
102
|
+
- VERSION
|
103
|
+
- lib/torque_box/sidekiq_service.rb
|
104
|
+
- lib/torquebox-sidekiq-service.rb
|
105
|
+
- test/helper.rb
|
106
|
+
- test/sidekiq_service_test.rb
|
107
|
+
- torquebox-sidekiq-service.gemspec
|
108
|
+
homepage: http://github.com/mogotest/torquebox-sidekiq-service
|
109
|
+
licenses:
|
110
|
+
- ASLv2
|
111
|
+
post_install_message:
|
112
|
+
rdoc_options: []
|
113
|
+
require_paths:
|
114
|
+
- lib
|
115
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
116
|
+
requirements:
|
117
|
+
- - ">="
|
118
|
+
- !ruby/object:Gem::Version
|
119
|
+
version: !binary |-
|
120
|
+
MA==
|
121
|
+
segments:
|
122
|
+
- 0
|
123
|
+
hash: 2
|
124
|
+
none: false
|
125
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
126
|
+
requirements:
|
127
|
+
- - ">="
|
128
|
+
- !ruby/object:Gem::Version
|
129
|
+
version: !binary |-
|
130
|
+
MA==
|
131
|
+
none: false
|
132
|
+
requirements: []
|
133
|
+
rubyforge_project:
|
134
|
+
rubygems_version: 1.8.24
|
135
|
+
signing_key:
|
136
|
+
specification_version: 3
|
137
|
+
summary: A TorqueBox service for running Sidekiq in the TorqueBox application server.
|
138
|
+
test_files: []
|