Simple ruby implementation of a Redis Reactor used for publish subscribe communication between celluloid actors using Reel websocket server

Ruby bindings for CGLM (https://github.com/recp/cglm), a high performance math library for graphics applications.

Parse changelog files and extract entries matching various criteria

A ruby interface to the CityBikes API v2. Returns data about bike-share networks and stations. Includes options to customize API requests.

helps read, write and remember commands.

Ruby wrapper for the context.io API.

Framework that provides a simple foundation for growing organically in the cloud

Ruby REST client for Delphix virtual database appliance

Communiceer met de API van DagjeWeg.NL en haal informatie op over dagjes weg

A gem for working with the Datacite XML format

DataStructures101 is a simple gem that groups several implementations of common data structures usually taught in Computer Science courses.

Track changes in your tables using PostgreSQL triggers..

Native implementation of Dijkstra algorithm for finding the shortest path between two vertices in a large, sparse graphs. Underlying algorithm is implemented in C using a priority queue. Edges are represented using linked lists rather than an adjacency matrix to reduce memory footprint when operating on very large graphs where the average number of edges between nodes is relatively small (e.g. < 1/10 the number of nodes). See https://en.wikipedia.org/wiki/Dijkstra's_algorithm for additional information.

A ruby binder for the Docdata Payment API.

Drift is a static blogging engine for Rails.

Use a YAML file to specify your API, and EasyApiDoc will serve up this information with executable examples.

Tools to make building API docs simpler.

Interface with message queues with ease.

# Error `Error` is a very small library that serves as a base `Class` for error `Class`es within your application. ## Install ### Bundler: `gem 'error'` ### RubyGems: `gem install error` ## Usage ```ruby ``` ## Contributing * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start a feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. ## Copyright Copyright © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details.

Eventually is an event library built to loosely mirror the NodeJS EventEmitter API.