watership 0.2.6 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 56677c57d836c14527c4f17df9988561f3972c27
-  data.tar.gz: 27ea7ce1bd196216472f2140a2fa4367ae01ef18
+  metadata.gz: e31ac67a5096eb488ad4e96d1ee7a7cacf73f968
+  data.tar.gz: b3133ac1edd479d1424e9f0cdc4dcbf25a333c05
 SHA512:
-  metadata.gz: ba65da99ea01c47e4b1da2cc9fde44f094c68178a028ec54301ea029eddf4e6a0de94da296e452c7fdce87d0635f9313ae9e03fc34702c3b30e5e19d533d0158
-  data.tar.gz: 97eed4dccb8d43e852fd196dd9bbcc0d9faabd859a6d8f2bf9c4c0c9e9ab7fa6a6839115f32e26239fe965324723896b522df3aaee36afa67e27757960ba820e
+  metadata.gz: 0ca4e4c3ec252205655b9cbdf1e0a2c72ae21161f2fe47e4a1734d1ca9e9d6be008135a2282e34846dd94f9a947247eaa1c95c125afafa812a6d78b11f97b6c6
+  data.tar.gz: c656ce8aa5f048ba6d74e571618824a6b7b8937bd60aaf748db3cd2bc8ad343e9d4055adff168bbc5a194a05c5953fb1f5062d5c24c2a2181964f3e04b7b171f

data/CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+## 0.3.0 - 2014-03-27
+* `Watership.config=` now takes a string representing an AMQP URI, not a path.
+
+## 0.2.6 - 2014-02-26
+* Exceptions are now only pushed to Airbrake from the `production` environment.
+* You can set Watership's environment with `Watership.environment = [env]`
+* You can set Watership's logger with `Watership.logger = [logger]`

data/README.md

@@ -22,25 +22,19 @@ Or install it yourself as:
 
 This is meant for our specific use case, but if you want to give it a go....
 
-Watership gives you channels. Instead of
+Once you've `require`d it, you configure Watership with:
 
-    client = Bunny.new([options])
-    channel = client.create_channel
+    Watership.config = '[AMQP URI]'
 
-You just do
+Optionally, you can set a logger (`Watership.logger = ...`) and specify the environment (`Watership.environment = ...`).
 
-    channel = Watership::Inle.connect([options])
+Then, connect to your RabbitMQ instance with:
 
-Watership doesn't automatically try to reconnect, but it does provide a couple of "helpful" methods:
+    Watership.reconnect
 
-* `Watership::Inle.ensure_connection` looks to see if you have a connection (that says it's connected), and if not will try to build one (pace some throttling). Note that the included fake client always reports that it's not connected.
-* `Watership::Inle.reconnect([boolean])` calls connect with the options originally provided, but allows you to pass `true` to force a connection to the fake.
+Finally, you push messages like this:
 
-## Naming
-
-Inlé is the Grim Reaper of rabbits in *Watership Down*.
-
-I always hear "rabbit" when someone refers to Welsh rarebit, so I think of it as a fake rabbit.
+    Watership.enqueue(name: 'queue name', message: 'message to enqueue')
 
 ## Contributing
 

data/lib/watership/version.rb

@@ -1,3 +1,3 @@
 module Watership
-  VERSION = "0.2.6"
+  VERSION = "0.3.0"
 end

data/lib/watership.rb

@@ -15,8 +15,8 @@ module Watership
       @env = env
     end
 
-    def config=(path)
-      @config = IO.read(path).chomp
+    def config=(uri)
+      @config = uri
     end
 
     def enqueue(options = {})

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: watership
 version: !ruby/object:Gem::Version
-  version: 0.2.6
+  version: 0.3.0
 platform: ruby
 authors:
 - Ben Scofield
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-26 00:00:00.000000000 Z
+date: 2014-03-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -74,6 +74,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitignore"
+- CHANGELOG.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -102,7 +103,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.0
+rubygems_version: 2.2.2
 signing_key: 
 specification_version: 4
 summary: Wrapper around Bunny to better handle connection issues