Simple ruby wrapper for pasing job feeds from Jobvite.com

Heavy metal Ruby SOAP client library

Permet de cataloguer, restaurer des fichiers photos et vidéos

Enables posting to GlueNow.com API service and reading posts from Glue accounts.

Allows you to extend MiniTest using reporters rather than monkey-patching

Freshbooks integration for Ruby

SQL client for any JDBC-compliant database. Written in JRuby.

Little library that encapsulates a (particular) standardised way of talking between a service and javascript. Probably not the best way of doing things, but it's been handy in a pinch.

Customizations for json_api_client 1.0.0 to handle 0.x servers

Create JSON documents with ease

An implementation of JSON patch in Ruby. http://tools.ietf.org/html/draft-pbryan-json-patch-01 Utilities for applying JSON patches to arbitary objects. To participate in the patch protocol, classes can implement #apply_patch

Get the color palette from sites

WWW::Delicious is a del.icio.us API client implemented in Ruby. It provides access to all available del.icio.us API queries and returns the original XML response as a friendly Ruby object.

Windows Azure Client Library for Ruby

Puppet spec helper and common rspec tests

A ruby application for setting up your k8s cluster as a load balancer.

Ruby client for interacting with kubernetes clusters

This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace

A high level Kafka client that supports producer, low level consumers, and high level consumers.

KalibroClient is a Ruby gem intended to be an interface for Ruby applications who want to use the open source code analysis webservice Kalibro.