Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Updated instructions for amqp installation. Require version >= 0.6.0.

+ Its preferable to install amqp gem from RubyForge
+ Minor update to README.rdoc related to --token

Signed-off-by: ezmobius <ez@engineyard.com>
  • Loading branch information...
commit 51d4185f12d7c7a1501a273caafb2d2c81f538b2 1 parent b4b3fe2
Glenn Rempe grempe authored ezmobius committed

Showing 2 changed files with 11 additions and 8 deletions. Show diff stats Hide diff stats

  1. +10 7 README.rdoc
  2. +1 1  Rakefile
17 README.rdoc
Source Rendered
@@ -105,6 +105,10 @@ Installing the gem gives us access to the various Nanite commands in the default
105 105
106 106 === Install AMQP Ruby Gem
107 107
  108 + # install version >= 0.6.0 from RubyForge
  109 + sudo gem install amqp
  110 +
  111 + # or install from source
108 112 cd <SRC>
109 113 git clone git://github.com/tmm1/amqp.git
110 114 cd amqp && rake gem && sudo gem install amqp-<VERSION>.gem
@@ -182,6 +186,9 @@ You can learn more about RabbitMQ admin here: http://www.rabbitmq.com/admin-guid
182 186
183 187 You can test that all the moving parts are working end-to-end by running one of the AMQP example programs. There are a number of example tests provided with AMQP but the one we will try simply queues and prints two messages immediately, and another one five seconds later.
184 188
  189 + # this test can only be run if you made a local clone
  190 + # of the amqp repository during the amqp installation above
  191 + # (it does not matter however if the gem was installed from src or rubyforge)
185 192 cd <SRC>/amqp
186 193 ruby examples/mq/simple-get.rb
187 194
@@ -211,14 +218,10 @@ Now run a mapper. Mappers can be run from within your Merb or Rails app, from a
211 218 cd examples
212 219 ./cli.rb
213 220
214   -Which should soon return something like the following. Note that the '55a7f300c454203eacc218b6fbd2edc6' in this example is the identifier for the agent that ran the task for you. This is auto-generated.
215   -
216   - {"55a7f300c454203eacc218b6fbd2edc6"=>"hello nanite"}
217   -
218   -Note : If you want the agents to run with a name you specify instead of the auto-generated id
219   -you can run them with something like the following (where bob is our unique id):
  221 +Which should soon return something like the following.
220 222
221   - nanite -t bob
  223 + {"bob"=>"hello nanite"} # where the '--token bob' parameter was passed
  224 + {"55a7f300c454203eacc218b6fbd2edc6"=>"hello nanite"} # where no '--token' was passed. auto-generated identity.
222 225
223 226 Now if you want to make this interesting, you can issue a Ctrl-c in one of the agent's windows to kill it. And then run cli.rb again. You should see that you still get a result back since the mapper is finding the remaining agent to do its work.
224 227
2  Rakefile
@@ -27,7 +27,7 @@ spec = Gem::Specification.new do |s|
27 27 s.executables = %w( nanite nanite-mapper nanite-admin )
28 28
29 29 s.add_dependency "extlib"
30   - s.add_dependency "amqp"
  30 + s.add_dependency('amqp', '>= 0.6.0')
31 31
32 32 s.require_path = 'lib'
33 33 #s.autorequire = GEM

0 comments on commit 51d4185

Please sign in to comment.
Something went wrong with that request. Please try again.