I'd need to see it, to be honest. It may be that there's a ton of repetition in the app, in which case templates will come to the rescue. But you're gonna have to deconstruct the app into MVC and effectively use it as a full-blown specification. I recon that will take you at least a week just to get a spec, probably a lot longer - what's the budget?
How many tables does it have? 100 pages implies 25 or so, assuming index + CRUD. Plus whatever SSI is adding in. Another thing to try is using a Rails app to created restful services and then calling back from the main app, but the original app sounds very user-centric so probably won't help. it might be better to refactor the existing app along restful lines and do some templating of your in readiness and leave it for now. On Wed, Jan 7, 2009 at 9:28 AM, Matt Roberts <[email protected]>wrote: > Hi all, > > I've been asked to make quite a lot of changes to an existing web site. At > the moment its all HTML with SSI's, and a wee bit of perl thrown in for good > measure. > > Obviously I want/have to to use rails to implement all the funky new things > they want, but I'm not sure how to tackle the current site. Should I try to > migrate the site properly into rails with nice url's and views for all the > pages (there seems to be a lot of those pages - over 100). Or should I try > to leave the current pages alone, and try to get SSI's working for those > pages (assuming that this is even possible in mod_rails with our hosting > provider).. > > Anyone had a similar dilemma? > > Matt Roberts > > > > -- Thanks and regards, Francis Fish --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
