Structuring customizations


#1

I’ve got a large project that I may be able to convert
to rails. The problem domain is a bit odd for most web
projects:

  1. There is a single data model.
  2. Each customer (~50), wants customizations to their
    web pages.
  3. 90% of the product is the same.
  4. There are several components to the product.
  5. Not all customers pay for each component.

If I use rails and create a “master” project. Do all
the main work as components, how do I structure each
of the customizations?

My question is specifically directed to how the
directory structure would look such that I don’t move
any files around and if a model is changed, the impact
to each customer can be tested.

Each customer will also have their own test cases for
the customizations performed.

Shawn G.


Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com