Extends CanCan with dynamic, inheritable permissions stored in a database, with caching and multi-tenant refinements

Database driven rules for CanCan

Simple authorization solution for Rails which is decoupled from user roles. All permissions are stored in a single location. This project is based off of Ryan Bates's CanCan Gem.

Unit test helpers for CanCan

Simple authorization solution for Rails which is decoupled from user roles. All permissions are stored in a single location.

Provides helpers to test via Rspec or any other test framework by stubing highline or in integration tests directly by handling STDIN AND STDOUT

Simple search using model scopes to create queries for ActiveRecord

A class for handling candlestick chart data

Simple feature flags based on a redis instance, a YAML config file and/or environment variables.

CanDo is a small gem to implement a simple user access system based on users, roles & capabilites, where: each user can have 0, 1 or many roles each role can have 0, 1 or many capabilites Users have capabilities by getting roles assigned (role == collection of capabilities). Within the code, the can helper method can be used to test whether a user has a certain capability or not (see below for a working code example).

An incredibly basic RPC system for Ruby

Candygram provides a job queue for the MongoDB document-oriented database, inspired by delayed_job and Resque. It uses the MongoMapper ORM and allows you to queue method calls for execution ASAP or at any time in the future.

Create Cane violations for pre-Ruby 1.9 hash syntax

A simple but handy key/value store which is able to use a bunch of SQL databases as its backend.

CanCan constraints for fields using strong_parameters

Dead simple canned configuration for gems or whatever

Cangrejo lets you consume crabfarm crawlers using a simple DSL

Provides a convenient hash for setting flags on your ActiveRecord models

Canister is a simple IoC container for ruby. It has no dependencies and provides only the functionality you need. It does not monkey-patch ruby or pollute the global namespace, and most importantly it expects to be invisible to your domain classes.

Profile based authorization for ruby on rails