HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ryanb
cancan
Ruby2011–2015
ryanb / cancan · Archived

cancan

Authorization Gem for Ruby on Rails.

7Distinct people
7Mentions
0Explicit recommenders
6.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Authorization Gem for Ruby on Rails.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2011-08-31 15:15:27 UTC to 2015-11-13 16:54:09 UTC.

0122011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC202
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101

What Hacker News says

7 sources
We're tracking Rails 4 compatibility for the major gems we use, based on a bit of skimming GitHub Issues and Pull Requests. Here are the highlights from that list: CanCan[1] has a '2.0' branch where Rails 4 support is being worked on. It also has PR #838 open for supporting strong_parameters in the current stable 1.6 tree. Devise[2] pushed 3.0.0.rc about a month ago with Rails 4 support. FriendlyId[3] seems to have work in progress on their master branch. Acts-as-taggable-on[4] states in their README that they are compatible in version 2.4.1, but there seem to be a couple open issues related to Rails 4. edit: formatting [1]: https://github.com/ryanb/cancan/ [2]: https://github.com/plataformatec/devise/ [3]: https://github.com/FriendlyId/friendly_id [4]: https://github.com/mbleigh/acts-as-taggable-on
In If Your Business Uses Rails 2.3 You Need To Move To A Supported Option ASAP
This might be premature, but I think what you're doing here is brilliant. I know so many designers-come-web-developers who struggle with the back-end portion of web development. Many use cases simply don't need the full flexibility of a web app framework, but do need more than what you can cobble together with outside tools like the various embeddable form tools and widgets. IMO, the authentication & authorization portion of your app is going to make or break the result. I'd like to make a suggestion. There is an authorization library for Rails named CanCan. It uses a declarative definition for authorization that is similar (loosely) to what you've got going right now. There is also an extension for CanCan called Cantango, which builds out the concept of roles as packages of permissions. Again, I'm speaking really loosely here, but it loo
Read the rest
ks like you're still working on this portion of the product, and these libraries work in a way that I think makes sense to your target market. The declarative style is a good fit for font end developers. You simply describe how you'd like users to interact with the API, and you're done. If you incorporated some of the ideas from these two libraries, I'd be really thrilled :) Can't wait to recommend this. https://github.com/ryanb/cancan https://github.com/kristianmandrup/cantango
In Dropbox deployment for front-end devs

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.