Rails For Legacy Apps
Upcoming SlideShare
Loading in...5
×
 

Rails For Legacy Apps

on

  • 2,084 views

 

Statistics

Views

Total Views
2,084
Views on SlideShare
2,083
Embed Views
1

Actions

Likes
0
Downloads
20
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Rails For Legacy Apps Rails For Legacy Apps Presentation Transcript

  • Patrick Crowley
  • Rails for Legacy Apps
  • (How to use Rails with existing apps)
  • • New ideas
  • •New ideas • No users
  • •New ideas • No users • Zero code investment
  • •New ideas • No users • Zero code investment • Best case scenario
  • But, in the real world...
  • • Legacy content
  • •Legacy content • Existing userbase
  • •Legacy content • Existing userbase • Front end (HTML + CSS)
  • •Legacy content • Existing userbase • Front end (HTML + CSS) • Database Schema
  • Q: How can I use Rails with a legacy app?
  • • Don’t! (Leave site as is)
  • • Don’t! (Leave site as is) • Reboot site with Rails
  • • Don’t! (Leave site as is) • Reboot site with Rails • Or, maybe...
  • Use Rails as a control panel to run your site
  • Case study: Cinema Treasures
  • Front-end Smarty Blogs Theater DB pMachine PHP/MySQL
  • How did we edit theaters?
  • phpMyAdmin (sadly)
  • • Intended for developers
  • • Intended for developers • Easy to harm database
  • • Intended for developers • Easy to harm database • Doesn’t scale
  • Why not roll your own?
  • • Not highest priority
  • •Not highest priority • Busy with other things
  • •Not highest priority • Busy with other things • I never want to write PHP again.
  • Let’s do it in Rails!
  • Basic concept
  • Current site Database
  • Current site Rails Database
  • Demo
  • Issues I ran into
  • • Non-plural table names
  • • Non-plural table names • Had to remove primary id’s on join tables
  • • Non-plural table names • Had to remove primary id’s on join tables • Needed a way to delete cached templates on db update
  • How long did this take?
  • 1 week / 2 - 3 hours per day
  • The End
  • New Theaters 6,000 4,500 3,000 1,500 0 2000 2001 2002 2003 2004 2005
  • New Comments 50,000 37,500 25,000 12,500 0 2000 2001 2002 2003 2004 2005