domains
D6 Internationalization: "Domain name only," Boost, multiple servers, and subdomains
There is a separate "primary" site (in another system [NOT Drupal]), and the Drupal site has two servers with one database on one of those servers connected to both Drupal instances. Our problem is with the two Drupal servers and DNS (domain/subdomain) settings to manage them.
One instance has a minute-by-minute CRON job running to keep the other in-synch, with rsync. Only one of those servers is open to login and edit with a subdomain pointing to it directly on the network. The other server has a read-only user setup for the database connection, just as a precaution.
One database, one main installation (shared modules, themes) -> many websites on different domains
To say less words and to be more clear, I've made a scheme of system, that I want to create.
If you've already made the same system, please, share your knowledge, and describe, how you did it.
If you just know how to do it, sure you are welcome to write as well.

Existing Domains and Multiple Site Module Control
I'm excited to begin working with this module. It has been quite the task to enable a module or change a permissions setting across 40 sites, having to log into each one or via update.php.
So my question is, how would this integrate into a collection of 30 - 40 established sites in a multisite configuration?
Is this something that needs to be implemented from stage 1?
I read the description of what the HM2 does but am still a little unclear how it handles modules.
Can I enable/disable modules via HM2?
Can I modify access controls across all domains and/or each domain via HM2?
multipul users
ok so we have plenty of people who are able to do a multi site install of Drupal where they are the host and the developer, or don't have others working on the same site. I have a situation where I have multipul users that should not have access to each others files and I don't want to have to create additional ftp accounts.
I am on a LAMP server and want to be able to offer my customers the option to have a 'one install to rule them all' set up, minimizing the time it takes to upgrade the system. Drupal 5's overrides system works great for this.



