Anonymous's picture
Posted by Anonymous on November 12, 2012 at 10:36pm
I am working on two projects at Cornell that might benefit from sharing one Drupal code base. The obvious options include:
- Common Drupal code / shared database (using Domain Access)
- Common Drupal code / separate databases (using Multi-site)
My questions:
- Does anyone have a recommendation about which approach is easier to maintain?
- Does the second option with separate databases make it easier to develop the multiple sites on separate time schedules?
Craig
Categories: domain access, Multi Site
Comments
Go with Multi-Site
One of the main advantages of Drupal is the separation of HTML from content. While content is rarely common across multiple sites, the code behind modules, and themes is common, and drupal has an elegant way of dealing with custom modules and subthemes. If you dig into your projects, you might find that you may need to further segregate content within a database using organic groups and context, but all the while you will still be using common code to render the content into html. Good luck.
I agree
I have done several shared code base sites now and tried both methods. You will find much less hassle in maintenance with the Multi-Site option.