I learn best by picking a project and learning a new technology by applying it to the project. This is how I originally learned PHP, MySQL, and various web technologies when developing the Detroit Curling Club site/portal. Looking back, it's amazing I got done what I did with what I knew. I implemented a Wiki, CMS, user management, uploading, RSS, and so forth, from the ground up, with no frameworks
However, the result also means the code is, shall we say, "spaghetti". And is really no fun to maintain and add to. Since then, I've learned Ruby and Rails and really enjoy working in the language and framework and wanted to reimplement the site. With so many other projects going on, I was concerned about the time necessary to get the site migrated.
Actually, it was rather easy. by stroke of fortune. Here is how the work went.
On the catwalk...
By similar mindset, when I designed the original database schema, I used "rails-esque" naming: tables are plural, columns are simple singular names. Join tables are alphabetical of the two tables they are joining. I just had to migrate the names of a couple of tables and columns to mee the rails standard configuration. I could have overriden the table/column names, but didn't want to deal with maintaining that. I really wanted the site to work like it was originally written with Rails in mind.
You've obviously created a Rails application by now, so I'll skip that. Now, I have my database (with backups). Setup your
config/database.yml to point to the database and then run
rake db:schema:dump to create the schema.rb of the database. If you want, you can copy this to a migration file.
Next, install Dr. Nic's Magic Models, which automagically give you your model files, associations, basic validations, and so forth with no coding. Magic just begins to describe it. You can verify this by bringing up
script/console and toying with your models and associations.
Testing is good
A good idea at this point is to load Selenium, a web user-interface testing application, and walk over your original site to create user interface requirements based on current site design. This should stand as your base-line specification. In the end, your Rails app should act like your current application.
You can also check out the work of Josh Susser who has a ruby script that will validate all the records in your database using your model validations.
Define your application test specification using RSpec and BDD. Again, you already have an existing web application to help define your desired functionality.
The View, the View
Now you have a your base application done. You should start migrating your views. Fill in your
layout/application.rhtmlwith the base layout from your original HTML files.
You'll now need to start actually defining your controllers for various functionality: calendar, users, leagues, etc. Along the way, run your tests you defined with RSpec and verify operation. This is where the actual work comes in. Overall though, I find the design of Rails to make this very easy going. I just have to deal with various legacy functionality.
Work in Progress
That all said, migrating the site has been very easy. So easy I'm looking at migrating other projects to Rails. Of course, deploying Rails applications to shared hosts is not nearly as easy as deploying PHP ones. Especially with applications that are meant for other users to easily install on their own hosts. But the ease of development and maintenance is not easily overlooked.
If only Apache supported a built-in Rails module. :)