cztop 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: eb0ba59995fcb10d5dd7054d72ba49cf886281ea
+  data.tar.gz: deea479538b525d5f92673bd694b8d34f5b8e7d8
+SHA512:
+  metadata.gz: 1849347983836cf93974f9f51d41147a1cacd6e4950b77b8ebac2a62429827b58fff40e8de41fe6c16cc44c8663c4009b8e20f44fe74c00956047885ccc21a73
+  data.tar.gz: e278d6d22d69c2e0f83bbaaed62057be6883a175749eee567aafd8343fde586cf3cb812c5e8e75e56ad56ec6808abd4617a907dc11f4ce06e5f1091fd167e4f7

data/.gitignore

@@ -0,0 +1,10 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/*.vimsession

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.travis.yml

@@ -0,0 +1,31 @@
+language: ruby
+sudo: false
+cache:
+  directories:
+    - $HOME/.ccache
+    - $HOME/.bundle
+rvm:
+  - 2.3.0
+  - 2.2.4
+  - 2.1.8
+  - jruby-head
+  - rbx
+env:
+  # recognized by czmq-ffi-gen's ci-scripts
+  - CZMQ_VERSION=HEAD ZMQ_VERSION=HEAD
+  - CZMQ_VERSION=3.0 ZMQ_VERSION=4.1
+matrix:
+  exclude:
+    # old ruby versions don't get to test bleeding edge functionality. basta.
+    - rvm: 2.2.4
+      env: CZMQ_VERSION=HEAD ZMQ_VERSION=HEAD
+    - rvm: 2.1.8
+      env: CZMQ_VERSION=HEAD ZMQ_VERSION=HEAD
+before_install:
+  - PATH="/usr/lib/ccache:$PATH" # enable ccache
+  - export LD_LIBRARY_PATH=$HOME/lib # custom libs (for execution)
+  - export PKG_CONFIG_PATH=$HOME/lib/pkgconfig # custom libs (for linking)
+  - export BUNDLE_PATH=$HOME/.bundle # bundle caching
+  - ci-scripts/install-deps
+  - gem install bundler -v 1.10.6
+script: bundle exec rake spec

data/.yardopts

@@ -0,0 +1 @@
+--private lib/**/*.rb - README.md LICENSE

data/AUTHORS

@@ -0,0 +1 @@
+Patrik Wenger <paddor@gmail.com>

data/CHANGES.md

@@ -0,0 +1,3 @@
+0.1.0 (23/01/2016)
+-----
+* first release

data/Gemfile

@@ -0,0 +1,10 @@
+source 'https://rubygems.org'
+gemspec
+
+# useful when working on czmq-ffi-gen in parallel
+#gem "czmq-ffi-gen", git: "https://github.com/paddor/czmq-ffi-gen.git"
+
+group :development do
+  gem 'rubocop', require: false
+  gem 'coveralls', require: false, platform: :mri
+end

data/Guardfile

@@ -0,0 +1,61 @@
+require "guard/rspec/dsl"
+
+# Start using
+#
+#   bundle exec guard -g doc & bundle exec guard -g spec
+#
+# This way you get parallel execution, so
+# * documentation is regenerated immediately
+# * specs are run immediately
+
+README_FILE = %r{^README\.md}
+
+# set these later using help from guard-rspec
+ruby_lib_files = nil
+spec_files     = nil
+
+# I don't need no shell that hogs my CPU whenever I hit return.
+interactor :off
+
+group :spec do
+  guard :rspec, cmd: "bundle exec rspec" do
+    dsl = Guard::RSpec::Dsl.new(self)
+
+    # RSpec files
+    rspec = dsl.rspec
+    watch(rspec.spec_helper) { rspec.spec_dir }
+    watch(rspec.spec_support) { rspec.spec_dir }
+    watch(rspec.spec_files)
+    spec_files = rspec.spec_files
+
+  #  # Ruby files
+    ruby = dsl.ruby
+    watch(ruby.lib_files) { |m| rspec.spec.(m[1]) }
+    ruby_lib_files = ruby.lib_files
+  end
+
+
+  puts "README pattern: %p" % README_FILE
+  puts "ruby lib files pattern: %p" % ruby_lib_files
+  puts "spec files pattern: %p" % spec_files
+end
+
+group :syntax_check do
+  guard :shell do
+    # check Ruby syntax
+    watch(Regexp.union(ruby_lib_files, spec_files)) do |m|
+      puts "Checking Ruby syntax of %p ..." % m[0]
+      if not system("ruby -c #{m[0]}")
+        n "#{m[0]} is incorrect", 'Ruby Syntax', :failed
+      end
+    end
+  end
+end
+
+YARD_OPTS = "--use-cache .yardoc/cache.db"
+
+group :doc do
+  guard 'yard' do
+    watch(Regexp.union(README_FILE, ruby_lib_files))
+  end
+end

data/LICENSE

@@ -0,0 +1,5 @@
+Copyright (c) 2016, Patrik Wenger
+
+Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

data/Procfile

@@ -0,0 +1,3 @@
+doc: bundle exec guard -g doc
+spec: bundle exec guard -g spec
+syntax_check: bundle exec guard -g syntax_check

data/README.md

@@ -0,0 +1,408 @@
+[![Build Status on Travis CI](https://travis-ci.org/paddor/cztop.svg?branch=master)](https://travis-ci.org/paddor/cztop?branch=master)
+[![Code Climate](https://codeclimate.com/repos/56677a7849f50a141c001784/badges/48f3cca3c62df9e4b17b/gpa.svg)](https://codeclimate.com/repos/56677a7849f50a141c001784/feed)
+[![Inline docs](http://inch-ci.org/github/paddor/cztop.svg?branch=master&style=shields)](http://inch-ci.org/github/paddor/cztop)
+[![Dependency Status](https://gemnasium.com/paddor/cztop.svg)](https://gemnasium.com/paddor/cztop)
+[![Coverage Status](https://coveralls.io/repos/paddor/cztop/badge.svg?branch=master&service=github)](https://coveralls.io/github/paddor/cztop?branch=master)
+
+# CZTop
+
+```
+_________  _____________________
+\_   ___ \ \____    /\__    ___/____  ______
+/    \  \/   /     /   |    |  /  _ \ \____ \
+\     \____ /     /_   |    | (  <_> )|  |_> >
+ \______  //_______ \  |____|  \____/ |   __/
+        \/         \/                 |__|
+```
+
+CZTop is a CZMQ binding for Ruby. It is based on
+[czmq-ffi-gen](https://github.com/paddor/czmq-ffi-gen), the generated low-level
+FFI binding of [CZMQ](https://github.com/zeromq/czmq) and has a focus on being
+easy to use for Rubyists (POLS) and providing first class support for security
+mechanisms (like CURVE).
+
+## Reasons
+
+Why another CZMQ Ruby binding? Here is a list of existing projects I found and
+the issues with them, from my point of view:
+
+* [Asmod4n/ruby-ffi-czmq](https://github.com/Asmod4n/ruby-ffi-czmq)
+  * outdated
+  * according to its author, it's an "abomination"
+* [methodmissing/rbczmq](https://github.com/methodmissing/rbczmq)
+  * no support for security features (see [methodmissing/rbczmq#28](https://github.com/methodmissing/rbczmq/issues/28))
+  * no JRuby support (see [methodmissing/rbczmq#48](https://github.com/methodmissing/rbczmq/issues/48))
+  * doesn't feel like Ruby
+* [mtortonesi/ruby-czmq](https://github.com/mtortonesi/ruby-czmq)
+  * no tests
+  * outdated
+  * doesn't feel like Ruby
+* [chuckremes/ffi-rzmq](https://github.com/chuckremes/ffi-rzmq)
+  * low level ZMQ gem, not CZMQ
+
+Furthermore, I knew about the generated low-level Ruby FFI binding in the
+[zeromq/czmq](https://github.com/zeromq/czmq) repository. I wanted to make use
+of it because I love that it's generated (and thus, most likely correct
+and up-to-date). Unfortunately, it was in pretty bad shape and missing a few
+CZMQ classes.
+
+So I decided to improve the quality and usability of the binding and add the
+missing classes. The result is
+[czmq-ffi-gen](https://github.com/paddor/czmq-ffi-gen) which provides a solid
+foundation for CZTop.
+
+## Goals
+
+Here are some some of the goals I have/had in mind for this library:
+
+- [x] as easy as possible, Ruby-esque API
+- [x] first class support for security (CURVE mechanism)
+  - [x] including handling of certificates
+- [x] support MRI, Rubinius, and JRuby
+- [x] high-quality API documentation
+- [x] 100% test coverage
+- [x] provide a portable Z85 implementation
+  * unlike [fpesce/z85](https://github.com/fpesce/z85), which is a C extension
+- [ ] use it to replace the [Celluloid::ZMQ](https://github.com/celluloid/celluloid-zmq) part of [Celluloid](https://github.com/celluloid/celluloid)
+- [ ] implement some of the missing (CZMQ based) Ruby examples in the [ZMQ Guide](http://zguide.zeromq.org/page:all)
+
+## Overview
+
+### Class Hierarchy
+
+Here's an overview of the core classes:
+
+* CZTop
+  * Actor
+  * Authentiator < Actor
+  * Beacon < Actor
+  * Certificate
+  * Config
+  * Frame
+  * Message
+  * Monitor < Actor
+  * Proxy < Actor
+  * Poller
+  * Socket
+    * REQ < Socket
+    * REP < Socket
+    * ROUTER < Socket
+    * DEALER < Socket
+    * PUSH < Socket
+    * PULL < Socket
+    * PUB < Socket
+    * SUB < Socket
+    * XPUB < Socket
+    * XSUB < Socket
+    * PAIR < Socket
+    * STREAM < Socket
+    * CLIENT < Socket
+    * SERVER < Socket
+  * Z85
+    * Padded < Z85
+
+More information in the [API documentation](http://www.rubydoc.info/github/paddor/cztop).
+
+### Features
+
+* Ruby-like API
+  * method names
+    * sending a message via a socket is done with `Socket#<<`
+      * `socket << "simple message"`
+      * `socket << ["multi", "frame", "message"]`
+    * `#x=` methods instead of `#set_x` (e.g. socket options)
+    * `#[]` where it makes sense (e.g. on a Message, Config, or Certificate)
+  * no manual error checking needed
+    * if there's an error, an appropriate exception is raised
+  * of course, no manual dealing with the ZMQ context
+* easy security
+  * use `Socket#CURVE_server!(cert)` on the server
+  * and `Socket#CURVE_client!(client_cert, server_cert)` on the client
+* socket types as Ruby classes
+  * no need to manually pass some constant
+    * but you can: `CZTop::Socket.new_by_type(:REP)`
+  * e.g. `#subscribe` only exists on CZTop::Socket::SUB
+* SERVER and CLIENT ready
+  * see CZTop::Socket::SERVER and CZTop::Socket::CLIENT
+  * there are `#routing_id` and `#routing_id=` on the following classes:
+    * CZTop::Message
+    * CZTop::Frame
+  * requires ZMQ >= 4.2
+* ZMTP 3.1 heartbeat ready
+  * `socket.options.heartbeat_ivl = 2000`
+  * `socket.options.heartbeat_timeout = 8000`
+  * requires ZMQ >= 4.2
+
+## Requirements
+
+You'll need:
+
+* CZMQ >= 3.0.2
+* ZMQ >= 4.0
+
+For security mechanisms like CURVE, you'll need:
+
+* [libsodium](https://github.com/jedisct1/libsodium)
+
+To install on OSX using homebrew, run:
+
+    $ brew install libsodium
+    $ brew install zmq  --with-libsodium
+    $ brew install czmq
+
+If you're running Linux, go check [this page](http://zeromq.org/distro:_start)
+to get more help. Make sure to install CZMQ, not only ZMQ.
+
+**Warning**: To make use of the full feature set of CZTop (including
+CLIENT/SERVER sockets and ZMTP 3.1 heartbeats), you'll need to install both ZMQ
+and CZMQ from master, like this:
+
+    # instead of the last two commands from above
+    $ brew install zmq  --with-libsodium --HEAD
+    $ brew install czmq --HEAD
+
+See next section.
+
+### Known Issues if using the current stable releases
+
+When using ZMQ 4.1/4.0:
+* no CLIENT/SERVER sockets. Don't try.
+* no ZMTP 3.1 heartbeats. Setting the options will have no effect.
+
+When using CZMQ 3.0:
+* don't use `Certificate#[]=` to unset meta data (by passing `nil`)
+  * `zcert_unset_meta()` was added more recently for that case
+  * see [zeromq/czmq#1248](https://github.com/zeromq/czmq/pull/1248)
+* if you use Beacon, make sure you also call `Beacon#configure`. Otherwise it closes STDIN when being destroyed.
+  * see [zeromq/czmq#1281](https://github.com/zeromq/czmq/issues/1281)
+* no CLIENT/SERVER sockets. Don't try.
+* no ZMTP 3.1 heartbeats. Don't try.
+
+### Supported Ruby versions
+
+See [.travis.yml](https://github.com/paddor/cztop/blob/master/.travis.yml) for a list of Ruby versions against which CZTop
+is tested.
+
+At the time of writing, these include:
+
+* MRI (2.3, 2.2.4, 2.1.8)
+* Rubinius (HEAD)
+* JRuby 9000 (HEAD)
+
+## Installation
+
+To use this gem, add this line to your application's Gemfile:
+
+```ruby
+gem 'cztop'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install cztop
+
+## Usage
+
+See the [examples](https://github.com/paddor/cztop/blob/master/examples) directory for some examples. Here's a very simple one:
+
+### rep.rb:
+
+```ruby
+#!/usr/bin/env ruby
+require_relative '../../lib/cztop'
+
+# create and bind socket
+socket = CZTop::Socket::REP.new("ipc:///tmp/req_rep_example")
+puts "<<< Socket bound to #{socket.last_endpoint.inspect}"
+
+# Simply echo every message, with every frame String#upcase'd.
+while msg = socket.receive
+  puts "<<< #{msg.to_a.inspect}"
+  socket << msg.to_a.map(&:upcase)
+end
+```
+
+### req.rb:
+
+```ruby
+#!/usr/bin/env ruby
+require_relative '../../lib/cztop'
+
+# connect
+socket = CZTop::Socket::REQ.new("ipc:///tmp/req_rep_example")
+puts ">>> Socket connected."
+
+# simple string
+socket << "foobar"
+msg = socket.receive
+puts ">>> #{msg.to_a.inspect}"
+
+# multi frame message as array
+socket << %w[foo bar baz]
+msg = socket.receive
+puts ">>> #{msg.to_a.inspect}"
+
+# manually instantiating a Message
+msg = CZTop::Message.new("bla")
+msg << "another frame" # append a frame
+socket << msg
+msg = socket.receive
+puts ">>> #{msg.to_a.inspect}"
+
+##
+# This will send 20 additional messages:
+#
+#   ./req.rb 20
+#
+if ARGV.first
+  ARGV.first.to_i.times do
+    socket << ["fooooooooo", "baaaaaar"]
+    puts ">>> " + socket.receive.to_a.inspect
+  end
+end
+```
+
+### Running it
+
+```
+$ ./rep.rb & ./req.rb 3
+[3] 35321
+>>> Socket connected.
+<<< Socket bound to "ipc:///tmp/req_rep_example"
+<<< ["foobar"]
+>>> ["FOOBAR"]
+<<< ["foo", "bar", "baz"]
+>>> ["FOO", "BAR", "BAZ"]
+<<< ["bla", "another frame"]
+>>> ["BLA", "ANOTHER FRAME"]
+<<< ["fooooooooo", "baaaaaar"]
+>>> ["FOOOOOOOOO", "BAAAAAAR"]
+<<< ["fooooooooo", "baaaaaar"]
+>>> ["FOOOOOOOOO", "BAAAAAAR"]
+<<< ["fooooooooo", "baaaaaar"]
+>>> ["FOOOOOOOOO", "BAAAAAAR"]
+$
+```
+
+## Documentation
+
+The API should be fairly straight-forward to anyone who is familiar with CZMQ
+and Ruby.  The following API documentation is currently available:
+
+* [YARD API documentation](http://www.rubydoc.info/github/paddor/cztop)
+
+Feel free to start a [wiki](https://github.com/paddor/cztop/wiki) page.
+
+## Performance
+
+Performance should be pretty okay since this is based on czmq-ffi-gen, which is
+reasonably thin.  CZTop is basically only a convenience layer on top, with some
+nice error checking. But hey, it's Ruby. Don't expect 5M messages per second
+with a latency of 3us.
+
+The measured latency on my laptop ranges from ~20us to ~60us per message for
+1kb messages, depending on whether transport is inproc, IPC, or TCP/IP.
+
+Make sure you check out the
+[perf](https://github.com/paddor/cztop/blob/master/perf) directory for latency
+and throughput measurement scripts.
+
+## TODO
+
+* [x] pack generated code into its own gem ([czmq-ffi-gen](https://github.com/paddor/czmq-ffi-gen))
+* think of a neat Ruby API, including:
+  - [x] Actor
+  - [x] Beacon
+  - [x] Certificate
+  - [x] Socket
+    - [50%] access to all socket options
+    - [x] Security mechanisms
+  - [x] Message
+  - [x] Frame
+    - [x] enumerable Frames
+  - [x] Authenticator
+  - [x] Loop
+  - [x] Monitor
+  - [x] Poller
+  - [x] Proxy
+  - [x] Config
+  - [x] Z85
+* write the missing XML API files in CZMQ
+  - [x] zarmour.xml
+  - [x] zconfig.xml
+  - [x] zsock_option.xml
+  - [x] zcert.xml
+  - [x] zcertstore.xml
+* [x] check availability of libsodium within CZTop
+* [x] read error strings for exceptions where appropriate (zmq_strerror)
+* [x] add support for ZMTP 3.1 heartbeats in CZMQ
+* [x] add padded variant of Z85
+* add more examples
+  * [x] [simple REQ/REP](https://github.com/paddor/cztop/tree/master/examples/simple_req_rep)
+  * [x] [Taxy System](https://github.com/paddor/cztop/tree/master/examples/taxi_system) with CURVE security and heartbeating
+    * [x] change from ROUTER/DEALER to SERVER/CLIENT
+  * [x] [Actor](https://github.com/paddor/cztop/tree/master/examples/ruby_actor) with Ruby block
+  * [ ] PUSH/PULL
+  * [ ] PUB/SUB
+* [ ] add performance benchmarks
+  * [x] inproc latency
+  * [x] inproc throughput
+  * [x] local/remote latency
+  * [ ] local/remote throughput
+  * see [perf](https://github.com/paddor/cztop/blob/master/perf) directory
+* [x] support older versions of ZMQ
+  * [x] ZMQ HEAD
+    * [x] tested on CI
+  * [x] ZMQ 4.1
+    * [x] tested on CI
+  * [x] ZMQ 4.0
+    * [x] tested on CI
+  * [ ] ZMQ 3.2
+    * too big a pain ([d5172ab](https://github.com/paddor/czmq-ffi-gen/commit/d5172ab6db64999c50ba24f71569acf1dd45af51))
+* [x] support multiple versions of CZMQ
+  * [x] CZMQ HEAD
+    * [x] test on CI
+  * [x] CZMQ 3.0.2 (current stable)
+    * no `zcert_meta_unset()` ([zeromq/czmq#1246](https://github.com/zeromq/czmq/issues/1246))
+      * [x] adapt czmq-ffi-gen so it doesn't raise while `attach_function`
+    * no `zproc`(especially no `zproc_has_curve()`)
+      * [x] adapt czmq-ffi-gen so it doesn't raise while `attach_function`, attach `zsys_has_curve()` instead (under same name)
+    * [x] adapt test suite to skip affected test examples
+    * [x] test on CI
+* [x] port Poller to `zmq_poll()`
+  * backwards compatible (`#add_reader`, `#add_writer`, `#wait` behave the same)
+  * but in addition, it has `#readables` and `#writables` which return arrays of sockets
+  * level-triggered (not sure if `zmq_poll()` itelf is, but it'll be trivial)
+  * could then be used in Celluloid::ZMQ
+  * want to use `zmq_poller()` because it can deal with CLIENT/SERVER sockets and is the future
+    * but can't use it because
+      * it doesn't allow me to get all readable/writable sockets back after one call to `#wait`
+      * can't just recall `#wait` with zero timeout until it says there are no
+	more, because ZMQ sockets (option ZMQ_FD) are edge-triggered :-(
+    * maybe I don't really need that functionality, though
+    * can't use `zpoller`, because it doesn't support polling for writing
+* [ ] add `Message#to_s`
+  * return frame as string, if there's only one frame
+  * raise if there are multiple frames
+  * only safe to use on messages from SERVER/CLIENT sockets
+  * single-part messages are the future
+* [x] get rid of Loop
+  * cannot handle SERVER socket
+  * there are other timer libraries for Ruby
+  * Poller can be used to embed in an existing event loop (Celluloid), or make your own trivial one.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/paddor/cztop.
+
+To run the tests before/after you made any changes to the source and have
+created a test case for it, use `rake spec`.
+
+## License
+
+The gem is available as open source under the terms of the [ISC License](http://opensource.org/licenses/ISC).
+See the [LICENSE](https://github.com/paddor/cztop/blob/master/LICENSE) file.

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -0,0 +1,7 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "cztop"
+
+require "pry"
+Pry.start

data/bin/setup

@@ -0,0 +1,7 @@
+#!/bin/bash
+set -euo pipefail
+IFS=$'\n\t'
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/ci-scripts/install-deps

@@ -0,0 +1,9 @@
+#!/bin/sh -x
+set -e
+mkdir -p vendor
+cd vendor
+git clone https://github.com/paddor/czmq-ffi-gen
+cd czmq-ffi-gen
+ci-scripts/install-libsodium
+ci-scripts/install-libzmq
+ci-scripts/install-libczmq

data/cztop.gemspec

@@ -0,0 +1,36 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'cztop/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "cztop"
+  spec.version       = CZTop::VERSION
+  spec.authors       = ["Patrik Wenger"]
+  spec.email         = ["paddor@gmail.com"]
+
+  spec.summary       = %q{CZMQ Ruby binding, based on the generated low-level FFI bindings of CZMQ}
+  spec.homepage      = "https://github.com/paddor/cztop"
+  spec.license       = "ISC"
+
+  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_runtime_dependency "czmq-ffi-gen", "~> 0.7.0"
+
+  spec.add_development_dependency "bundler", "~> 1.10"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec"
+  spec.add_development_dependency "minitest"
+  spec.add_development_dependency "rspec-given", "~> 3.8.0"
+  spec.add_development_dependency "pry"
+  spec.add_development_dependency "yard"
+  spec.add_development_dependency "guard"
+  spec.add_development_dependency "guard-rspec"
+  spec.add_development_dependency "guard-yard"
+  spec.add_development_dependency "guard-shell"
+  spec.add_development_dependency 'terminal-notifier-guard'
+  spec.add_development_dependency 'foreman'
+end