Thanks for your help. When you do the engine/mountable app do you have to copy the codebase from one into the other or can you simply reference the other codebase? If upgrading the existing app is too much, do you have any other recommendations for user/api app moving forward?
Thanks On Fri, Dec 2, 2011 at 1:41 PM, Hassan Schroeder <[email protected] > wrote: > On Fri, Dec 2, 2011 at 10:04 AM, Roger R. Smith <[email protected]> > wrote: > > > based on your experience what would be the best way to move forward: > > > > 1) move the models to a plugin? > > 2) use Rails Engine? > > 3) re-write everything? > > 4) build the api/new user interface on top of the existing app? > > I think it's hard to say definitely without knowing more about the app, > but my inclination would be to upgrade the whole thing to 3.1, which > will also give you the opportunity to clean up the code. > > Then you can take advantage of the Engine/mountable app approach > if it still makes sense. It seems like that would depend on the degree > of coupling between the admin/user/api parts, but -- by the time you > finish writing tests and upgrading, you'll be in a much better position to > evaluate that :-) > > HTH, and good luck, > -- > Hassan Schroeder ------------------------ [email protected] > http://about.me/hassanschroeder > twitter: @hassan > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
