A Ruby CardDAV client library (RFC 6352).

Wrapper for Cardinity's HTTP payment API.

The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.

CLI for cardmarket.com

Card Validator - simple card validator

Cli that helps you install dependencies in your Cargo.toml just like npm does.

Build clean, robust and consistent forms for Caring.com.

Carnivore HTTP source

Carnivore RabbitMQ source

Command executor

Gem helps add any number of items to customer's shopping cart and direct him to Amazon website to complete order.

Connect to CarrierBot API

Store CarrierWave files in PostgreSQL (supporting multiple versions per uploader).

Add storage support for Tencent COS to CarrierWave

carriots api wrapper

Carrousel is a robust utility designed to take a list of generic items, and given some command, perform that command on each item in that list. Depending on the commands return value, Carrousel will track which items have been completed successfully, and retry items as necessary. It will save your progress in a status database and you can quit the loop and come back later to finish unprocessed items.

CarryOut connects units of logic into a serial execution. Each unit can extend the DSL with parameter methods. Artifacts and errors are collected as the series executes and are returned in a result bundle upon completion.

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.

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.

This release is the *last* version of cartage-rack. It will be replaced with a different tool in the future, but this release will allow installation in modern Ruby versions. cartage-rack is a plug-in for {cartage}[https://github.com/KineticCafe/cartage] to provide a Rack application that reports on release metadata. 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. The package is created with its dependencies bundled in +vendor/bundle+, so it can be deployed in environments with strict access control rules and without requiring development tool access.