Enforces DDL/migration safety in Ruby on Rails project with an emphasis on explicitly choosing trade-offs and avoiding unnecessary magic.

A library to control and query Philips Hue lights

Lightweight, opinionated wrapper for using RabbitMQ headers exchanges

A simple network emulator with capabilities similar to mininet.

PiecePipe is about breaking your problem into its smallest, most interesting pieces, solving those pieces and not spending time on the glue code between them.

Fantozzi REST API client

Pipedrive API client for Ruby. Full API NOT implemented currently.

Generate dependency graphs from pipeline definitions.

Utility to encrypt and decrypt messages using OpenSSL::PKCS7

Ruby client for PlanetScale Databases

This gem provides all necessary tools to make a Rails application into a platform with third party applications.

Boilerplate-reduction helpers for Poise/Halite-style gemss.

HTTP stub as DSL

Ruby gem wrapper for https://pokeapi.co/api/v2/

Polist is a gem for creating simple service classes and more.

AWS polly wrapper, converts from text into speech audio.

Poper makes sure that your git commit messages are well-formed

It is a Rails engine that gathers a set of other gems and configurations designed to build incredible APIs

Ruby wrapper for the Power BI API

Backtrace (Stack traces) are essential information for debugging our applications. However, they only tell us what the program did, but don't tell us what it had (the arguments, local variables...etc.). So it's very often that we'd need to visit each call site, rerun the program, and try to print out the variables. To me, It's like the Google map's navigation only tells us the name of the roads, but not showing us the map along with them. So I hope to solve this problem by adding some additional runtime info to the backtrace, and save us the work to manually look them up.