Is this group working?

Some of us are here and yes, some of us even have a multi-install up and running... The instructions found in the Drupal handbook are pretty good, albeit confusing in a few places...

It turns out that this sort of install is totally at the mercy of your server situation. If you're like me and you're using a hosting company, there's a lot of grey area in setting multisites up. Trying to figure out just what part of the settings you need to tweak leads to lots of headscratching.

But once I'd realized that I needed to set up my "secondary" sites as redirects with my hosting company, everything just worked out fine!

So go ahead and ask your questions - I'll be glad to answer what I can!

Hey, fellow drupalers-

iterative improvement process:

1. purpose
2. measurements
3. strategy
4. goals (back to purpose)

iterative design process:

1. requirements (based on purpose, measurements)
2. design
3. build
4. test (back to requirements)

I'd like to establish the requirements of a multisite configuration, so that I can better design and build the components. In order to efficiently embark on this work, I need to establish the "purpose, measurements, strategy, goals" of this type of configuration. I've found that due diligence in these areas provide massive dividends later.

So, are there any of you out there that are familiar enough with a multisite configuration that you feel comfortable articulating (in a few sentences) the "purpose" of a multisite configuration as well as the "measurements" that can be evaluated to establish whether the multisite configuration is fulfilling it's purpose.

After the purpose and measurements are established we can move to "strategy" and "goals". And then on to -> "requirements".

Necessity and sufficiency logic statements can be useful:

Necessity logic:
"In order for a multisite configuration to be successful, it must(1, 2, 3,...).

After a list is compiled - on the sufficiency logic:

Sufficiency logic:
"If, and if, and if, (x number of and if statements), then a multisite will be successful"

This doesn't have to be hard, as we can always iterate/spiral through.

I feel strongly that multisite configuration issues will be/are important to future Drupal development, and would like to see things get started off on the right foot.

So, with all that said, maybe we could start with the necessity logic stuff:

"In order for a multisite configuration to be successful, it must(1, 2, 3,...).

As a community, we could work on this list. Sound good?

========
Doug Ouverson

I started this drupal group because I've been using this feature, and it's pretty hard to use, and there was no group discussing it! I started a few other groups around that time because I was about to get into some heavy development with a couple major projects, then I got sidetracked.

I got no feedback for a long time, then someone emailed me saying he wants to do a multisite tutorial and I replied saying I'd help, but never heard from him again. I'd still like to help, but as I told him, I'm limping by with the rest of you though I'd make a great proofreader and tester.

Someone mentioned that there are no docs whatsoever for non-Apache servers. Unfortunately I only use Apache. I'd like to help create a unified document. The hardest kind of stuff, currently, is stuff like this (from my own experience): To get my subdomain to be recognized by Drupal, I had to rm -rf my subdomain's directory and replace it with a symlink to my main site's www directory.

How do we get this type of advice/hack/whatever to people using Windows servers, and how do we not have to do this type of hack in the first place?

Thanks,

Mike