By pk_uk on

I've been reading up about 'Multi Sites' and the 'Domain'. I'm not sure which way to go.

I want to manage several sites - mainsite.com, othersite1.com, othersite2.com (Subdomains is NOT an option for business reasons). I would also like single sign-on. Will be using Linux shared hosting, at least to start with, so won't have access to Apache configuration files etc.

(1) Single code base, multiple databases appeals but I am concerned about upgrades. I guess I would run the upgrade on the main site. However, would I have to run the upgrade process against all sites. If so, could it be automated (how)?

(2) The same with new modules. If I install through the main site, do I then have to enable on each of the sites/run an upgrade process on each site?

(3) I understand about putting appropriate entries in the site subdirectory of mainsite.com but I'm not so sure about how I set-up othersiten.com so that it redirects (I understand about DNS etc and have access to DNS settings)

(4) I want to share content on some sites, if possible. Might it be possible with multi-sites e.g. by some sites sharing the same database - or are there issues I'd need to be aware of if I only want some of the content shared from a database?

(5) If issues with 4, alternatively, could Domain and multi-site be mixed e.g. mainsite.com use one database for content and othersite1.com and othersite2.com share a database, but all run off the same codebase.

Thanks in advance for your attention.

Paul K

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

1) yes. automation, unsure, but with drush and likley some version control it's not that big a deal.

2) yes.

3) point the docroot of the site to the folder that holds the code base

4) sharing tables in the DB is done with the array in settings.php

5) based on what you are asking for , I'm beginning to think you want aegir.