Bebox is a project born from the necessity of organizing a way to deal with the provisioning of remote servers. Bebox is based on puppet and much like another quite known project Boxen, the idea is to have a good agreement on how to manage a puppet repo for a remote environment. It is also a good idea to have a standard approach on dealing with the provisioning problem, including how to write modules, integrate them into the projects, a directory structure for the projects to follow, how to have a replicated 'development/test' environment into virtual machines, etc.

a set of tools for the bussy bee - CVS

Have associations between ActiveRecord objects and MongoMapper documents

Provides an interface for uploading data to BigQuery.

Interface with Bing Content API for managing Shopping Ads.

Использование инфоблоков 1С-Битрикс в Ruby On Rails проектах

Ruby-esque handling of Bitcoin wallet

DSL for buisness processes.

Blazy(be lazy) is a fluent extension to active record models to reduce number of key strokes in rails console

Add a blog to your Rails application in minutes with this mountableRails Engine

Provides an interface to the YouTube API.

Brick Layer interface for templates, helpers, and client like use cases.

plugin for pipeline that provides importers and models for migrating data to bsi

Opinionated toolbox for building centralised authorities

Bundle many ActionMailer messages for the same recipient into a single email

Upload a spreadsheet, map its headers to your columns, and create database objects with the correct associations.

API consuming models for the Biola Web API project

Calil api wrapper.

The all-new Basecamp has an all-new API. It is not compatible with the Basecamp Classic API.

Caperoma automates many decisions related to the programming that you often don't realize, and which you can forget hundreds of times during the time of working on the project: pulling the latest code from upstream before you start working, remembering from which branch you started the feature to later make a pull request into it, creating & starting tasks in Jira, creating & starting tasks in Pivotal, naming branches, adding Jira ID into the branch name, style guide checks, commits, naming commits, adding Jira ID into commit name, adding Pivotal ID into commit name, git pushes, pull requests into correct branches, stopping tasks in Jira, stopping tasks in Pivotal, tracking time, logging time to Jira, switching back into the original branch and much more.