Fork of ruby_core_source modified to support CFLAGS and permit use of whichever build system (mkmf, rpmkmf, or other modules) while utilizing core source. This fork was created because the existing ruby_core_source takes over the build definition, preventing definition of CFLAGS and other settings that mkmf requires be defined by an enclosing block.

INPUT, FILTER, OUTPUT data with RULES and code

A simplified pattern to execute rails applications within Docker (with a CI build emphasis)

BoxGrinder Build Tarball Platform Plugin

Prune is meant to analyze a folder full of files, run them against a retention policy and decide which to keep, which to remove and which to archive. It is extensible and embeddable.

Show the changes between two .gem files

Automatically launch Hadoop or Spark clusters in the cloud

hexlet cli

Description of Hyrax::Ingest.

Dumps mongodb databases and archives them.

ssh driver for test-kitchen for any Linux based Cisco platform with an ip address Works the same as kitchen-ssh but adds a prefix_command directive to prefix a string before every command. Useful for changing network namespace (hint, hint)

Resolves cookbook dependencies

Resolves cookbook dependencies

A Bundler for your Chef Cookbooks that does not depends on chef.

Upload and download LXC containers from S3

Shared LXD Container Access Library

In-memory tar archive creation

Mingle 3.3 introduced a new Events API in the form of an "Atom feed":http://www.thoughtworks-studios.com/mingle/3.3/help/mingle_api_events.html. The Mingle team and ThoughtWorks Studios are big believers in the use of Atom for exposing events. Atom is a widely used standard, and this event API style puts the issue of robust event delivery in the hands of the consumer, where it belongs. In fact, we'd argue this is the only feasible means of robust, scalable event delivery, short of spending hundreds of thousands or millions of dollars on enterprise buses and such. Atom-delivered events are cheap, scalable, standards-based, and robust. However, we do accept that asking integrators wishing to consume events to implement polling is not ideal. Writing polling consumers can be tedious. And this tedium gets in the way of writing sweet Mingle integrations. We are addressing this by publishing libraries such as this, which if effective, fully hide the mechanics of event polling from the consumer. The consumer only need worry about the processing of events. Said processing is modeled in the style of 'pipes and filters.'

Gem for easy log rotation and S3 upload

WIP: This gem is not ready yet.