Posted by Matt
on March 16, 2008
RESTful_ACL has moved from Google Code to GitHub! Why the move? Well, it’s basically due to git being the new black, and more fun than Subversion. I’m in the process of migrating all of my repositories.For anyone who hasn’t tried git yet, please do. It’s super simple yet really powerful. You can even import your existing Subversion repos to git by simply doing
git svn clone user@host:/path/to/repo
Try it! It won’t screw your existing SVN repo. Honest.So without further adieu,
Here is RESTful_ACL’s new home and for the impatient, you can clone the repo via:
git clone git://github.com/mdarby/restful_acl.git
Posted by Matt
on March 02, 2008
Just a quick note to say that RESTful_ACL has been updated. This latest version supports securing non-CRUD actions. It’s a slight cop out of sorts; essentially if the user in question can read an object, they will also be able to do the non-CRUD action. It’s not the best solution to the problem, but it will work for the moment. Maybe there is a slick way to pass in a function name as a hash/block thing that I’m not sure of. Hrm.
Posted by Matt
on February 19, 2008
Just a quick update to let you know that RESTful_Acl has been updated. I removed the mapped urls option in favor of manually opting out of the ACL check on actions that are to be public. The full write-up can be found at the usual location. Just a heads up!
Posted by Matt
on February 08, 2008
I’d like to announce my very first Ruby on Rails plugin; RESTful_Acl.RESTful_Acl is a simple Access Control Layer for Ruby on Rails, it allows you to restrict access on a fine-grained level to any RESTful MVC stack. While the ACL structure and engine are provided by this plugin, the implementation is fully up to the user. Every application is different and everyone likes to setup their User / Account / Role resources differently; this plugin will allow you to do your thing and keep that thing locked down.The full write up is available here!
