EdgeCloud

After posting the mandatory Rails upgrade yesterday, the team turned around and rolled out 1.1.6. The comments thread, again, is awash in, erm, comments. Given the interesting issues with each upgrade in the 1.1.x series (check out the work from 1.1.2 and 1.1.3) everyone now seems a little upgrade shy. Stuff happens, the team is working hard, let’s move along…nothing to see here…

One more for the road…Get your upgrade on!

1. RailsConf Planet
2. Foreign Keys and examining the drinking of the DHH Kool-Aid
3. Link Out to Josh Susser who’s working on the same problem domain
4. Rails Plugin for foreign keys
5. A last link out on an STI issue

And that’s from one (count ‘em, one) article on the railsconf log. (And, yes, the particular issue above is something near and dear to my heart - I happen to think referential integrity is a Good Thing™ though I think a willigness to debate the common wisdom is good.) I have lots to go there as there’s just tons of info to absorb from everyone who took part at RailsConf this year. Thanks to every one of those folks for sharing as it is invaluable to those of us who weren’t able to click the submit button fast enough for signup. I’m looking forward to finding more gems…

The Locomotive project on Mac OS X promises to deliver a fully self-contained, easy to install, dmg for installation of Rails on Mac OS X. What’s interesting is this piece:

Simultaneously run multiple versions of Rails, each of which may be configured with different libraries, gems, or web servers. Locomotive uses “Bundles”, each of which is a self-contained installation of Ruby, Rails, and all the necessary support software and libraries (as well as many useful optional tools!).

I think that’s great, especially if you need to run different projects under different environments - this makes it that much easier on the mac.

The enthusiasm from the Locomotive site is well-founded - it is easy to install (drag and drop like any other Mac App) and works out of the box without a problem. I was able to do a local svn co of a project and point Locomotive to it without a problem. One tip though: if you can’t get it to start out of the box and you aren’t doing a new rails project locally but instead are checking out an existing project from a repository somewhere then check your permissions. It could be that you don’t have the appropriate permissions on the project in question. That will save you 5-10 minutes of pulling out your hair.

Locomotive is a Universal Binary.

Yeah, I mean literally “throwing it.”

We started up our first rails project recently which meant that we had to get the project into subversion. This wasn’t a particular problem in and of itself but I did have some interesting moments going through code to see what needed to be svn:ignore’d so we’d have a “clean” checkout when any of us needed to do so. This bash script from Jonathan Shea on textsnippets.com would have done the trick. I was able to piecemeal some parts together manually to get what I wanted out of it. A look through the script looks like it would have done all the dirty work for us and will be in our arsenal with whatever project is around the corner.