Blazing Cloud hosted a “Do One Thing for Rails 3″ bugmash and Workshop curriculum hacksession. We had four participants:
We followed wycats instructions for getting started. Some pre-conditions that weren’t spelled out:
- Ruby 1.8.7 is required, which implies a re-install of rubygems (you need 1.3.5+) and your gems as well [sudo] gem install bundler
Rails 3 discoveries
1) Karen and I discovered that cucumber doesn’t work with Rails 3 — the generator isn’t available so we couldn’t even get started. I added that to the gem compatibility list. Also, I didn’t report it, but noticed that the script/generate help isn’t given when you pass no params.
$ ./script/generate cucumber
Could not find generator cucumber.
Please select a generator.
Builtin: active_record:migration, active_record:model,
active_record:observer, active_record:session_migration, app,
controller, erb:controller, erb:mailer, erb:scaffold, generator, helper,
integration_test, mailer, metal, migration, model, model_subclass,
observer, performance_test, plugin, resource, scaffold,
scaffold_controller, session_migration, stylesheets, test_unit:controller,
test_unit:helper, test_unit:integration, test_unit:mailer,
test_unit:model, test_unit:observer, test_unit:performance,
2) Sharon discovered what appears to be an incompatibility between bundler and XP Home.
3) The very first time I did scaffold, I got an “ActionController::InvalidAuthenticityToken” error when I ran the app and tried to create a new record, but when I dropped the database and tried to reproduce it worked fine.
Things we learned that have nothing to do with Rails 3
- bundler is not only a gem, but also a plugin to RubyGems
- cucumber (post 0.4.5) is split into two gems: cucumber and cucumber-rails