It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible! If you truly want that flexibility: http://github.com/stephencelis/kvc

Another replacement for factories and fixtures

Fixtures replacement with scenarios

Open-source Dropbox using Ruby and Git (my fork with github favoured markdown support).

Migration helper extensions for Ruby On Rails development

ActiveRecord/Rails Sphinx library

Searchlogic provides common named scopes and object based searching for ActiveRecord.

A simple and complete ACL system for Rails, that allows to specify a role for an user for a single resource.

Control which columns are loaded when preloading associations; prevents N+1 queries while reducing memory usage.

Fast webserver log parser for persisting daily pageviews per path to sqlite

Fast webserver log parser for persisting daily pageviews per path to sqlite

High performance ActiveJob Queue Adapter for PostgreSQL that provides maximum reliability and ACID compliance

Datamining Bot

A command-line tool to search Skype history.

Search and retrieve Skype conversations from the cli

Gem for notifying slack about the creation and updation of ActiveRecord models.

Website crawler harvesting e-mails. Uses Sidekiq and Typhoeus.

An ORM using the Data Mapper pattern, specifically built to solve Digital Repository use cases.

This rubygem does not have a description or summary.

Slimak creates slugs from multiple model attributes (slug_columns) and supports storing them in the DB with uniqueness and fast lookup.