Duane Morin
2009-Feb-10 21:18 UTC
What''s the pattern for modularizing / sharing your code?
Ok, this is the first time I''ve run across this, but I think they''re good problems to have :). I''ve got a web app out in production. I''ve also got a tool for internal use that manages the reporting on that application. Problem #1: What''s the best practice out there for sharing the model? They are entirely separate web apps with entirely different users, environments, and purpose - but they both manipulate the same business model. Surely there is a way to avoid repeating myself? Problem #2: With the success of the first production webapp, the boss said "Ok, now tell us what it would take to do the exact same thing for our other, differently-branded web site." Ummm....short of "clone all the source code" I was a bit stuck for an answer. Here it seems like there''d be even more overlap, but I''m not sure about the reality - it would be all new views, but also at the very least some new configuration to differentiate it from its twin in the database. Is there a better answer there? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---