The Halloween Edition
One of the first tutorials I’ve seen that focuses on Rails 2.0.
This would seem to make deploying a Rails app on Amazon’s
EC2 on Rails is an Ubuntu Linux server image for Amazon’s EC2
hosting service that’s ready to run a standard Ruby on Rails
application with little or no customization. It’s a Ruby on Rails
virtual appliance. If you have an EC2 account and a public keypair
you’re five minutes away from deploying your Rails app.
A collection of Rails links
This is a nice step-by-step article on integrating
PayPal with your Rails application, using
I’ve only skimmed over the new features in the upcoming 2.0 release of
Rails, but this looks like one of the nicest features. This is a good
explanation of how it works and why it’s useful.
A bugfix release of Mongrel is out. Looks like 1.1 is due soon, and it
“Mongrel 1.1 is coming real soon now with JRuby support and a few
Being a bit of an Emacs junky, I’m not sure how I missed this. Looks
mature, and very functional, and almost TextMate-like. The link has a
nice flash video of Emacs on Rails in action.
Sitepoint’s book “Build Your Own Ruby on Rails Web Applications” is now
free, at least for the next month. I’ve only skimmed it, but it looks
like a decent introduction, and the price is certainly right.
Update: I somehow managed to misspell Relevance’s name. Fixed.
I’m missing RailsConf this year (I have no excuse, I live two hours
away). I’m living vicariously through the other attendees though,
keeping an eye on the blog posts.
One announcement that I just caught was that
Relevance has announced
Streamlined, which is a
framework on top of the Rails framework. Some of the interesting
features include (pulled from Justing Gehtland’s
- Generator for churning out the initial views and configuration
- A declarative DSL for managing views, including relationship
management, field selection, etc.
- Full Ajax-enabled management views with sorting, paging and live
search (with configurable field-inclusion)
- An extensible component system for representing relationships at
runtime * REST-ful web service layer around all models
- Auto user-management and inclusion of declarative role-based
It looks like this gives you a really good jumpstart on building data
driven applications (as if Rails wasn’t enough of a jumpstart). The
management views in particular sound nice
(Django has this already, really the
only thing Django has over Rails as far as I can tell).
They’re planning on realeasing this at OSCON in July. I’m looking
forward to it.
A few links that caught my eye today:
An introduction to Ruby on Rails for DB2 developers
- Nice article if you’re a DB2 user and want to know what the fuss is
about. Written by Edd Dumbill.
Ruby-Gnome2 Website - Appears to
be a decent GUI toolkit for Ruby. I wish someone would get QT’s Ruby
bindings working on Windows. The thing I miss most about Python is
Sapphire in Steel: The Little Book of Ruby - Nice
introduction to Ruby with plenty of code samples, in PDF form.
Ruby Cookbook -
The Perl Cookbook, ported to Ruby.
Ruby Inside - A great new blog by Peter
Cooper, focused solely on Ruby. The last two items
came from this site. I don’t know how he finds all these cool links.
Configuring Rails Environments - The Cheat Sheet
- Now you can find out what all of those neat settings in
There’s a relatively
comparison of the Django
framework to Rails over at
Sam Newman’s site. It appears
to be a relatively fair comparison.
It’s interesting that both frameworks were extracted from large
development projects in roughly the same time period, although Rails has
been publicly available for longer, and has more mindshare at the moment.
I’m happy with Rails, but I wonder whether I would have bothered with it
if Django had been available when I started looking at Rails. The thing
that kept me away from Rails for a long time was that I didn’t know
Ruby. I was (and still am) well-versed in Python. I still prefer the
cleaner syntax of Python over Ruby, although the latter does have some
features that I find compelling.
I wonder about the impact of one aspect of Django though: the fact that
the model generates your databas schema, instead of the developer
generating the model from the schema (which is the Rails model). I
suspect most DBA’s would go into convulsions at the very thought of
this. I can certainly see how it would ease moving from database to