Pre-flight Checklist

Version 8 (Ed Ruder, 08/01/2009 10:38 pm)

1 1
h1. Pre-flight Checklist
2 1
3 4 Mike Gunderloy
The only real requirement for participating in a BugMash is enthusiasm. But there are some things you can do in advance to make it a more productive and rewarding experience.
4 1
5 4 Mike Gunderloy
h2. Required Software
6 1
7 4 Mike Gunderloy
* Ruby. In general, Ruby 1.8.6 or Ruby 1.8.7 at a reasonably current patch level is fine for working on Rails. However, if you want to help check on cross-Ruby-version issues, you'll need to have multiple copies of Ruby and a way to switch between them. Fortunately Relevance has provided some "easy instructions and utilities":http://blog.thinkrelevance.com/2009/7/29/ruby-switcher-working-with-multiple-ruby-versions-has-never-been-this-easy for doing just that.
8 4 Mike Gunderloy
* RubyGems. You need to be on the cutting edge to work with the Rails source - 1.3.5. Run @gem --version@ to check your version and, if necessary, @gem update --system@ to upgrade.
9 4 Mike Gunderloy
* Rails. You presumably have some version of Rails installed, but to participate, you'll need the Rails source. And because we're concentrating on Rails 2.3.x issues, you need the correct branch of the source. Here's how:
10 4 Mike Gunderloy
11 5 Mike Gunderloy
<pre>
12 4 Mike Gunderloy
git clone git://github.com/rails/rails.git
13 7 Ed Ruder
cd rails
14 4 Mike Gunderloy
git branch --track 2-3-stable origin/2-3-stable
15 4 Mike Gunderloy
git checkout 2-3-stable
16 5 Mike Gunderloy
</pre>
17 4 Mike Gunderloy
18 6 Mike Gunderloy
* Mocha. The Rails tests depend on mocha for mocks, so @gem install mocha@.
19 4 Mike Gunderloy
* MySQL. Having a working MySQL install is the bare minimum to run the tests on Rails.
20 8 Ed Ruder
* "PostgreSQL":http://www.postgresql.org/download/ and sqlite. If you're planning to work on Active Record issues, you'll need to run the AR tests across MySQL, PostgreSQL, and sqlite at the very minimum.
21 4 Mike Gunderloy
22 4 Mike Gunderloy
h2. Accounts
23 4 Mike Gunderloy
24 4 Mike Gunderloy
* You'll need an account with Lighthouse to comment on "Rails issues":https://rails.lighthouseapp.com/projects/8994-ruby-on-rails or to upload tests or patches. Sign up "here":https://rails.lighthouseapp.com/login
25 4 Mike Gunderloy
* You don't need a "Github account":https://github.com/signup/free unless you start doing such extensive surgery that you want to have your own fork of the Rails repo. (Note that the Rails team only accepts patches, not pull requests)
26 4 Mike Gunderloy
27 4 Mike Gunderloy
h2. For Windows Users
28 4 Mike Gunderloy
29 2 Mike Breen
Windows users can find an installation guide over at the "devChix":http://wiki.devchix.com/index.php?title=Server_2003 wiki. (You can skip steps 11 and 12 for setting up Heroku.)
30 1
31 4 Mike Gunderloy
h2. Optional Components
32 1
33 4 Mike Gunderloy
* If you'd like to help the JRuby-on-Rails story, you'll need to have "JRuby":http://jruby.codehaus.org/ installed. Note that the Relevance switcher mentioned above can do this for you.
34 4 Mike Gunderloy
* If you're brave enough to test ActiveRecord with JDBC connections and databases, "this ticket":https://rails.lighthouseapp.com/projects/8994/tickets/1685-adding-ar-test-connections-for-jdbc-via-jruby will point you in the right direction.
35 4 Mike Gunderloy
* If you do a great deal of work with Lighthouse, you may find the OS X application "Lighthouse Keeper":http://www.mcubedsw.com/software/lighthousekeeper useful.
36 1
37 1
Back to [[BugMash]]