Navigate Chrome browser sessions and execute JavaScript using CDP via Chromate, with session persistence

A Ruby client for interacting with the Bucket API to upload and list files

This gem has been removed and deprecated due to incompatability with Buildium's business practices.

CLI for Buildkite, similar to gh for GitHub

Bunny CDN API

The worst Ruby web framework

A BusTime API wrapper to retrieve bus routing and prediction info from transit authorities such as the Chicago Transit Authority (CTA).

LangChain but for the builder tech stack.

Concise and readable unit tests

A tiny lispey type of thing for learning purposes.

miniature rails for anyone

An alternative approach to index & search with Elasticsearch & Ruby on Rails

Capistrano plugin for managing environment variables with teller

Provides a ruby interface to interact with the cardknow API

categoria presents a set of generators for domain-driven development in rails

CCCUX provides a comprehensive admin interface and user experience layer for CanCanCan authorization. It includes role-based access control (RBAC) models, admin controllers for managing users, roles, and permissions, and a clean interface for authorization management.

Access water station data from USGS, Colorado DWR, TWDB, and other water agencies

Chagall is a deployment tool for Rails applications, optimized for development and production single-server docker/podman compose setups.

ChangeRequests puts an approval gate in front of any action in your Rails application. Instead of running a guarded operation immediately, you record it as a change request — the service class, the method, and its arguments — and it stays pending until one ore more other actors approve. Nothing executes until someone other than the requester has signed off. Each request moves through a guarded lifecycle: pending, approved, successful or failed, with cancellation and comments available at any point before it reaches a final state. Every transition is a small command object that validates the actor's permissions and the current status before touching the record, so invalid transitions raise rather than silently succeed. Failed requests keep their approval and can be retried. The engine makes no assumptions about your user model. You tell it which controller methods return the current actor and their permissions, choose which routes to mount, and it stays out of the way of the rest of your app. Reference views ship with it for a working approvals screen, and every one of them can be replaced or overridden without forking the gem.

Charming brings Rails-like application, routing, controller, and rendering conventions to Ruby terminal user interfaces.