multisite

Hi,

I am hoping you can help me. I work for a university and have recently been assigned to a project working with on-line community portals built using Drupal. I am trying to set up a sandbox system that I can play with, so that I don't mess up the actual sites. The problem I am having is setting up multisites using the same code base. I can get a single site set up and running just fine, however every time I try and set up multisites everything stopes working. I have followed all the instructions I can find on-line including these from the Drupal site:

I have a question about a multi-site folder setup, and bazaar workflow.

I'm thinking of setting up a bzr repository for each individual site, and then a repository for the sites/all folder, plus one for core. Does this sound like an acceptable way to do it?

Then, onto the symlinks:

Firstly, is it best practice to store each individual site folder as a symlink?

For example, say this is my sites folder:

sites
-all
-default
-site1.com
-site2.com

I am currently using git to manage my site-specific projects, e.g. code that lives under /sites in a multisite (single core) scenario.

However, I find myself needing to work on two things that will require a separate repository tracking the Drupal core: 1) one-off core patches, and 2) install profiles.

I can't think of a better title sorry...

I'm using the (excellent) Domain Access module. One thing I'm doing is aliasing sites. As an example.co.uk is aliased to example.com. So going to example.co.uk/foo is identical to going to example.com/foo.

However, there are one or two pages (in a large site) which I want to be different. So example.co.uk/contact would go to a different page than example.com/contact.

The "easiest" way (if horrendous in some respects) seems to be to add code (to theme_preprocess_page? to settings.php? custom_url_rewrite_inbound?) that says:

Hello, I'm a newbie in the world of web-design, and 3 month ago I had an idea of a site which i now what to put it in practice. The great idea:

1. 4 domains
   • domain1.tld
   • domain2.tld
   • domain3.tld
   • domain4.tld
2. 6 subdomains, the same 6 for each of the domains
   • subdomain1.domainX.tld
   • subdomain2.domainX.tld
   • subdomain3.domainX.tld
   • subdomain4.domainX.tld
   • subdomain5.domainX.tld
   • subdomain6.domainX.tld

As posted as an issue in location (http://drupal.org/node/610620)

<

blockquote>
The way location_instance is a multi-type table, storing both uids and nids, means it's (nearly) impossible to share this table between 2 sites...

A typical multi-site shared db does something along the lines of this:

DB A - Only Nodes in Site A , Shared Users
DB B - Only Nodes in Site B, Shared Users
DB User - shared with both A & B, contains user tables, sessions, and other tables that are user related, so both sites can access non-node based info.

Hello

Hello,

I am looking for ideas to organize SCM and development workflow for distributed teams with aegir/multisite environment.

Here is some initial thought:

• Each developer will have multisite or even aegir environment if applicable;
• Staging/production server will have aegir;
• Every custom website will have it's own scm(we using git), for custom theme at least and custom modules at most;

Now developers have to checkout sites into their local environment and push it back when they done.

Hi there,

Is there a simple way to split off a subsite from a multisite installation? I'd like to hand off hosting of a site I created for a friend, but I'm having some issues with peeling it off my D6 multisite.

I figured I could just dump the database, copy the files and hand it over, but there seems to be problems with paths. (Doesn't help that the live URL has to point to my multisite until the standalone is ready.)

I've found a few sorta similar issues on the boards, but haven't been able to find a definitive answer (or at least one I can get to work.)

Thanks,
Kevin

UPDATE Network Manager has been released for 5 6 and 7.
I'm releasing a new module soon and wanted to get some feedback on a screencast that I did. It's a project called the Network Manager (http://drupal.org/project/network_manager) and it helps you manage / maintain your sites all from within one site (given permissions set correctly for mysql user).

Here are links to the screencast (Jing forces it to be in 5 minute segments) --
Part 1 - http://bit.ly/PGu8J
Part 2 - http://bit.ly/yR6Zy
Part 3 - http://bit.ly/BLWrU