By Anonymous (not verified) on

I have a brand new hosting account (apache).
I have two domains that will eventually be hosted on this account.
From the information on my host's website I'll be using a Drupal "parked multisite" installation to run both.
I'd like both domains to have their own database and theme.
Right now I am only dealing with one domain. I'll get it up and running and then some months down the line bring the next domain over.

I've inquired with my host about how I need to configure Drupal initially. They say:
>>Setting up the first site properly is quite helpful.
Simply make sure you use Multisite for the first one.<<

I assume that means the very first domain I bring to this account needs to be configured in it's own subdirectory:
sites/example1.com
as opposed to
sites/default

I'm not sure that that's what I interpret from the instructions I read here on Drupal.org. I'm not so sure that they don't discuss installing Drupal "normally" for the first domain (sites/default/settings.php) and then sites/example2.com/settings.php for the second.

If both methods are possible, does one offer advantages over the other?
Thanks

⋅ Categories: Drupal 7.x

Comments

vm’s picture

vm commented

one thing to consider about multiple sites running on one code base is that when you update a module shared on more than one site or update core itself both sites need to be put in maintenance mode. If something breaks it's possible that both sites go down until it's fixed.

IMO multisites are best for generating a production site and a dev site.

the 1st site is typically installed from the code base in the domain's public root (not in a /sites/subdirectory).

Anonymous’s picture

Anonymous (not verified) commented

thanks