gorg_service 2.0.0 → 2.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 05925a6b430592a5e9c01f98423987239a0302d7
4
- data.tar.gz: 55dd773958591108940af27364b2c5707f0d1209
3
+ metadata.gz: 8d535b2cc33297465224d92a6ac703ea8f3cd9ad
4
+ data.tar.gz: 1f02ef04616fc0c50f9d4846e8a48dcb629f7ee8
5
5
  SHA512:
6
- metadata.gz: a06683f30182e6942c534c87d4fecea0203ba2e869e8fa1f94ce2d824c7ec6d5454e34b189488312505973d0a6c6c24ed1b5653a2fb73e10ed93569e2334a9c0
7
- data.tar.gz: c315f15ab148e9309252d75d4867bd929aa76e7704cf54fb3dee7afb7abbc865283d941732579fbee7217bad23ac382f9369bd04e67164cb6f5ff37bea56d32d
6
+ metadata.gz: b02477efe24f9ea170358e2f7a00167cc0b07e8f7b7c3d777bf84e27c4ecc290a57860a2eff3d28d3d7202f5a753e74ce3e6f41a74c01be90ec970d47cd58be1
7
+ data.tar.gz: a67d51f7cabdb9a1ffbb76cf7622fd39da3075168564c1ca336f452f5f5dada2a27fa1d036930451f9b541ed449f8442eac59f2a474237838c377abdcdf345a8
data/README.md CHANGED
@@ -42,6 +42,7 @@ GorgService.configure do |c|
42
42
  #
43
43
  # c.rabbitmq_host = "localhost"
44
44
  # c.rabbitmq_port = 5672
45
+ # c.rabbitmq_vhost = "/"
45
46
  #
46
47
  #
47
48
  # c.rabbitmq_queue_name = c.application_name
@@ -81,7 +82,7 @@ my_service.run
81
82
  When running, GorgService act as a consumer on Gadz.org RabbitMQ network.
82
83
  It bind its queue on the main exchange and subscribes to routing keys defines in `message_handler_map`
83
84
 
84
- Each received message will be routed to the corresponding `MessageHandler`. AMQP wildcards are supported.The first key to match the incomiing routing key will be used.
85
+ Each received message will be routed to the corresponding `MessageHandler`. AMQP wildcards are supported.The first key to match the incoming routing key will be used.
85
86
 
86
87
  A `MessageHandler` is a kind of controller. This is where you put the message is processed.
87
88
  A `MessageHandler` expect a `GorgService::Message` as param of its `initializer`method.
@@ -28,7 +28,7 @@ Gem::Specification.new do |spec|
28
28
 
29
29
  spec.add_dependency 'bunny', '~> 2.2', '>= 2.2.2'
30
30
  spec.add_dependency 'json-schema', '~> 2.6'
31
- spec.add_dependency 'gorg_message_sender', '~> 0'
31
+ spec.add_dependency 'gorg_message_sender', '~> 1'
32
32
 
33
33
  spec.add_development_dependency "bundler", "~> 1.11"
34
34
  spec.add_development_dependency "rake", "~> 10.0"
@@ -2,5 +2,5 @@
2
2
  # encoding: utf-8
3
3
 
4
4
  class GorgService
5
- VERSION = "2.0.0"
5
+ VERSION = "2.0.1"
6
6
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gorg_service
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.0
4
+ version: 2.0.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Alexandre Narbonne
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2016-05-31 00:00:00.000000000 Z
11
+ date: 2016-06-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: bunny
@@ -50,14 +50,14 @@ dependencies:
50
50
  requirements:
51
51
  - - "~>"
52
52
  - !ruby/object:Gem::Version
53
- version: '0'
53
+ version: '1'
54
54
  type: :runtime
55
55
  prerelease: false
56
56
  version_requirements: !ruby/object:Gem::Requirement
57
57
  requirements:
58
58
  - - "~>"
59
59
  - !ruby/object:Gem::Version
60
- version: '0'
60
+ version: '1'
61
61
  - !ruby/object:Gem::Dependency
62
62
  name: bundler
63
63
  requirement: !ruby/object:Gem::Requirement