Pacifying overactive records

You can setup the check when a password can be reused by a user. It lets you configure the last 'n' password can not be used by user when they change it.

An activeModel Validator that provides a quick and easy way to validate a password against a user defined schema

Module that defines a tree data structure based on a path.

Cliente do Pato

Patriach is about adding behaviours on the fly to good old active record models.

Patriach is about adding behaviours on the fly to good old active record models.

Ruby gem developed to help with pagination, filtering, sorting, and including associations on both active record queries and custom sql queries

Using Peacekeeper, you can develop models separately from the ORM used to persist data.

Introduces ActiveRecord to PostgreSQL, adding support for PostgreSQL specific features.

Percent objects and integration with Rails

Allows to use percona in rails migrations.

Helpers for using pt-online-schema-change with Rails.

Repository/Entity pattern conventions.

Repository/Entity pattern conventions. This is an adapter for ActiveRecord.

Continous integration solution compatible with travis.ci

This is a gem originated from another gem called permalink. Since I often want a permalink that provides no way to tell the database ids, I came up with the idea about encrypting the id and prepending it to the permalink. For more information about FPE(Format Preserving Encryption), please consult the wikipedia. The encryption method of current release is simply RC4-40 with a configurable key. Note, RC4-40 is not a strong encryption algorithm at all, and you shouldn't rely on it to delivery sensitive information. Also, to prevent inconsistance of encryption, and duplication(although the chance is very low) you should keep your key as a secret and never change it. The original implementation of generating permalink involves a infite loop to check uniqueness in database. It's slow, inefficient and most importantly, it still can't prevent race condition. And since we are using a FPE algorithm on the database id, which is garanteed to be unique from database, we don't need to put ourselves in that inefficient loop. Finally, what's the purpose of this gem? It's only a gem that helps hiding your database ids.

Generate permalink attributes on ActiveRecord, based on Permalink gem by Nando Vieira

Persists Ruby Objects with an ActiveRecord model

Provide a database-backed enumeration between indices and symbolic values. This allows us to have a valid foreign key which behaves like a enumeration. Values are cached at startup, and cannot be changed.