I've recently started learning about how to setup a multi-site drupal web page.
I am working on a web site for a national veterans organization. The question has come us asking if the different states can be part of the site. The national site name would be SOA.COM. The Florida State site would be either FL.SOA.COM or SOA.COM/FL - probably the first.
At this point, I do not have a question about how to set it up, but the practicality of this approach.
The idea is we would share the code across all fourteen sites, but we would NOT share data. This means that I would have 14 different databases, with 14 different set users, and 14 different administrators (plus the master admin for all sites).
The idea is, by using the multi-site capabilities I would reduce my software maintenance. However, this means that I would have to upgrade all 14 sites at the same time. Which means I have the opportunity to break all 14 sites at the same time if the upgrade causes any problems (of course this would never happen).
From what I've read, there are also some potential security issues where one of the administrators could gain access to data in the other sites.
I like the idea of 14 different site because it resolves the security issues and I can only break one site at time. However, the mere thought of having to maintain the software on 14 sites sounds is causing me to have nightmares. Fortunately, 13 of these sites will be using base modules with little or no custom code.
So my question is: While saving time on the software maintenance sounds like a great idea and time saver, is this a practical approach in the real world?
Or are there better approaches?