Matt, M.S.

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!

I’ve been listening to Happy Hardcore all day, so it might have had something to do with perking my brainwaves all on up. Whatever it was, today was fucking awesome.

Today I successfully created a proof of concept Rails application that uses FancyUpload, MooTools, Amazon AWS, attachment_fu, and mimetype_fu. This application allows seamless multi-file uploads to attachment_fu (which generates thumbnails flawlessly) and in turn stores the files to AWS’s S3 service.

To any non-programmers, this is probably not interesting, but shit, I had to do this by hand in PHP less than a year ago and I’m still battling with it. Enter Rails (and some brilliant plugins) and I have the whole damn thing up in a few hours. Not to mention that the whole upload/download is ultra secure and replicated across the globe with basically 99.99999% uptime. That beats my halfassed server petting zoo at the office by about six nines!

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!

So it seems that my MacBook (2Ghz Core2 Duo, 2G RAM) runs 4707 Rspec tests in 67.5 seconds. My CentOS server (4200+ Core2 Duo, 2GB RAM) runs the same tests in 91.7 seconds. Both are running the latest version of MySQL. How odd is that?