Rails For Legacy Apps

  • Published on
    16-May-2015

  • View
    1.320

  • Download
    0

Transcript

<ul><li> 1. Patrick Crowley </li></ul> <p> 2. Rails for Legacy Apps 3. (How to use Rails with existing apps) 4. New ideas 5. New ideas No users 6. New ideas No users Zero code investment 7. New ideas No users Zero code investment Best case scenario 8. But, in the real world... 9. Legacy content 10. Legacy content Existing userbase 11. Legacy content Existing userbase Front end (HTML + CSS) 12. Legacy content Existing userbase Front end (HTML + CSS) Database Schema 13. Q: How can I use Railswith a legacy app? 14. Dont! (Leave site as is) 15. Dont! (Leave site as is) Reboot site with Rails 16. Dont! (Leave site as is) Reboot site with Rails Or, maybe... 17. Use Rails as a control panel to run your site 18. Case study: Cinema Treasures 19. Front-endSmarty Blogs Theater DBpMachinePHP/MySQL 20. How did we edit theaters? 21. phpMyAdmin(sadly) 22. Intended for developers 23. Intended for developers Easy to harm database 24. Intended for developers Easy to harm database Doesnt scale 25. Why not roll your own? 26. Not highest priority 27. Not highest priority Busy with other things 28. Not highest priority Busy with other things I never want to writePHP again. 29. Lets do it in Rails! 30. Basic concept 31. Current site Database 32. Current siteRails Database 33. Demo 34. Issues I ran into 35. Non-plural table names 36. Non-plural table names Had to remove primaryids on join tables 37. Non-plural table names Had to remove primaryids on join tables Needed a way to deletecached templates ondb update 38. How long did this take? 39. 1 week / 2 - 3 hours per day 40. The End 41. New Theaters 6,000 4,500 3,000 1,5000 2000 2001 2002 2003 2004 2005 42. New Comments 50,000 37,500 25,000 12,500 020002001 2002 2003 2004 2005 </p>