Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt. The package is created with vendored dependencies so that it can be deployed in environments with strict access control rules and without requiring development tool presence on the target server(s). This is the last release of cartage. It's been a fun ride, but Docker-based images are our future at Kinetic Commerce. There is one feature that remains useful, the release-metadata output. We have created a new, more extensible format for which we will be creating a gem to manage this. One example of the implementation can be found at: https://github.com/KineticCafe/release-metadata-ts We will also be replacing `cartage-rack` with a new gem supporting this new format.

kinetic_cafe_error provides an API-smart error base class and a DSL for defining errors. Under Rails, it also provides a controller concern (KineticCafe::ErrorHandler) that has a useful implementation of +rescue_from+ to handle KineticCafe::Error types. Exceptions in a hierarchy can be handled in a uniform manner, including getting an I18n translation message with parameters, standard status values, and meaningful JSON representations that can be used to establish a standard error representations across both clients and servers.

This gem provides a way to create a dynamic usable DSL framework representing your website or app. Implementing Selenium/Appium driver and YAML configurations, this API will provide a layer in between your automation code and the driver. By creating YAML configurations that represents your website/app, the DSL framework in turn will reflect your configuration and allow you to control the automation through the DSL framework. Using this gem can help remove tedious tasks that are often repeated throughout code and help improve the scalability of code by mapping UI in YAML configuration files.

Ballot provides a two-way polymorphic scoped voting mechanism for both ActiveRecord (4 or later) and Sequel (4 or later).

cartage-bundler is a plug-in for {cartage}[https://github.com/KineticCafe/cartage] that uses Ruby {Bundler}[http://bundler.io] to install application dependencies into the <tt>vendor/bundle</tt> path to allow for clean deployments in environments with strict access control rules and without requiring development tools on production servers. Cartage provides a repeatable means to create a package for a server-side application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt.

cartage-s3 is a plug-in for {cartage}[https://github.com/KineticCafe/cartage] to upload the built package to Amazon's S3 or a service with a similar interface. Cartage provides a repeatable means to create a package for a Rails application that can be used in deployment with a configuration tool like Ansible, Chef, Puppet, or Salt.

Bonus assertions for {Minitest}[https://github.com/seattlerb/minitest], providing assertions I use frequently, supporting only Ruby 2.0 or better.

Stockpile is a simple key-value store connection manager framework. Stockpile itself does not implement a connection manager, but places expectations for implemented connection managers. So far, only Redis has been implemented (stockpile-redis). Stockpile also provides an adapter so that its functionality can be accessed from within a module. Release 2.0 fixes an issue when Stockpile options are provided with an OpenStruct, originally reported as {stockpile-redis#1}[https://github.com/halostatue/stockpile-redis/issues/1]. Support for Ruby 1.9 has been dropped.

stockpile-redis is a connection manager for Redis to be used with {Stockpile}[https://github.com/halostatue/stockpile].