One of Drupal's most powerful enterprise-level features is its "multisite" capability, which allows running numerous Drupal websites off of a single code base. This makes managing code-level changes extremely easy, although there is still some manual work needed to migrate database changes and create new sub-sites. There are a number of tools available for Drupal that make managing multi-site installations easier. This task is to compare and contrast those tools.

As there are a wide number of possible use-cases for multi-site, consider in particular the following use case: Different departments in an organization want to run their own sites off of a single code base. Each department wants a completely independent instance of Drupal (no shared tables or content). However, each department will be launching at a different time. The main administrator wants to be able to roll out a new "skeleton" site for a department on request, with a default theme (which the department can customize if desired) and some default pages and menu items pre-created (an about page, a contact page, etc.).

Select and compare at least three (3) tools and modules for multi-site management given the above use case, such as Hostmaster2 or Druplet, with regards to the following criteria:

- Ease of installation and ease of use.
- Available features and functionality.
- Flexibility to handle use cases other than the one described above.
- Extensibility for future use (including upgrade potential to later Drupal versions).
- If the tool or module is still in development, it's potential for successful completion.

For this task you may use either Drupal 5 or Drupal 6.

The deliverable for this task is a written report detailing each reviewed tool and a conclusion recommending one based on the criteria above. The task is complete when it has been posted to the Drupal Documentation issue queue and marked fixed (accepted) by a member of the Documentation Team. (ODT or RTF format preferred.)

Resources:
- http://drupal.org/getting-started/5/install/multi-site
- http://groups.drupal.org/hm2
- http://drupal.org/project/druplet

Estimated time: 4 to 5 days
Mentor: Larry "Crell" Garfield

http://code.google.com/p/google-highly-open-participation-drupal/issues/...

Comments

webchick’s picture

Title: GHOP #XX: Review multi-site manager tools » GHOP #66: Review multi-site manager tools

subscribing

add1sun’s picture

Status: Active » Postponed (maintainer needs more info)

Claimed by danielskeenan.

DragoonBoots’s picture

Before I start on the report, what is the format of the report? (i.e. Length)

Crell’s picture

As long as it needs to be in order to fully cover the required information. :-) (Do I sound like a teacher yet?) Both long prose and lists are useful, where appropriate.

I would say for each tool reviewed, include a description of the tool, how it works, what it can do, etc. Then compare them against each other and justify a conclusion as to which is best to use.

Have a look at the writeup for the penetration testing task: http://drupal.org/node/197142#comment-646340 . That one was extremely well-received (read: we all loved it), so I'd say that's a good model to follow.

DragoonBoots’s picture

You sound like one of the good English teachers I've had. :-) I'm working on an outline now, and will post it here and to the Google issue page as soon as I finish it. As of now, I'm looking at 5 paragraphs (introduction, one for each tool, and conclusion) with screenshots of each tool, as well as a table comparing the three near the end in the conclusion.

DragoonBoots’s picture

I'm having some trouble getting HostMaster2 to work, So the outline will probably get posted around mid-tomorrow.

Crell’s picture

Thanks for the update. I'm definitely down with a comparison table.

Also, don't feel constrained to 5 paragraphs. Approach it as 5 sections, each of which is however long (however many paragraphs) it needs to be. You'll get better grammar that way, too, since frequently breaking an idea into multiple paragraphs makes it easier to digest. (They don't teach you that in English class either, do they? :-) )

DragoonBoots’s picture

Might make sense. I've almost got the outline done (My computer hates me), so I'll see if it seems like I'm cramming to much into too little.

DragoonBoots’s picture

StatusFileSize
new99.63 KB

Just finished cleaning up the outline.

Crell’s picture

Thanks, Daniel. The outline looks like a good start, with one caveat. I wouldn't really call installation profiles an MSM; they're just automation scripts for installing a single site, whether that site is part of a multi-site install or not. They can certainly be used by MSMs, but they are not themselves an MSM. You'll need to track down a 3rd option as well. I'm pretty sure there is one, but I can't remember its name off hand. :-) Stop by #Drupal if you need help tracking it down, as someone has probably heard of it. Covering Install Profiles as part of the writeup as well, though, is perfectly fine.

Also, I presume you will be covering what about Hostmaster2 is so annoying to set up? How do each of these tools handle subdirectory- vs. subdomain-based multisites? (That is, example.com/subsite vs. subsite.example.com.)

I look forward to the full version!

Crell’s picture

Hi Daniel. Any word on your progress?

DragoonBoots’s picture

Due to some nasty mid-term stuff, I haven't gotten to work on this all that much. My goal is to have the thing completed by the end of this weekend.

DragoonBoots’s picture

StatusFileSize
new87.82 KB

This is the final outline for the review. The review itself will hopefully be done sometime tomorrow.

DragoonBoots’s picture

StatusFileSize
new86.4 KB

Done!

aclight’s picture

Status: Postponed (maintainer needs more info) » Needs work

I took a look at this and have some comments:

A.)

It has not yet seen a stable release, and requires checkout from the CVS repository.

If it requires checking out from the repository there is *no* release, not just no stable release.

B.) In footnote #1 on page 1, I'd like a title there also, so it's clear what the footnote is for.

C.) Page 2, at the top, refers to the security risk. This seems like a huge risk to me, and you might emphasize this more.

D.) Page 2: "Once past the ins" instead of "Once past the installation" is what I see in my document.

E.) Page 2 bottom: "but it is not as powerful as Druplet and Hostmaster2". Why not? You could expand a little here.

F.) Your table could use a bit more vertical padding so the text from different cells doesn't run together (this is probably only a problem when it's printed).

This looks like a good draft. Hopefully Crell will chip in with some comments as well and you can get this done soon.

DragoonBoots’s picture

Status: Needs work » Postponed (maintainer needs more info)

I'll work on those problems tonight. I printed out the last page to check out issue F, and I do agree. I'll see what looks good for that one.

DragoonBoots’s picture

StatusFileSize
new86.73 KB

Updated the draft. I'm calling this "Draft 2" until Crell gets a chance to look at it.

Crell’s picture

Status: Postponed (maintainer needs more info) » Needs work

Re #17:

- Please use section headers to differentiate each part of the report, as that makes it easier to read.

- Some of the language feels rather informal. I prefer more formal language for this sort of summary. (e.g., "works pretty well", "Create content song and dance", etc.).

- You say Druplet will "probably be released soon". Do you have a source for that? Did you talk to the maintainer to get a release plan? If not, please do so. If so, state as much in the report. ("According to its maintainer, SomeDude, a beta should be released around X.")

- There's a spelling error or two. :-)

- So how does Druplet actually work? It uses installation profiles, but what does it do with them? How does one create a new site? Is there a way to secure it in production? A multi-site manager that can't be used in production is not super useful. :-)

- For HM2, what "things" need to be checked out, and what's so complicated about svn? :-) Is the documentation for HM2 lacking?

- For MM, you say it uses the same "create content song and dance" as Druplet, but you don't say what that is in either case.

I'd like to see a lot more detail on each option. So far it looks like you're presenting the conclusion for each (Druplet is easy but insecure, Hostmaster2 is hard, Multisite Manager is easy and secure usually), but not any of the reasoning behind your conclusion. That reasoning is important, as it helps people evaluate if the trade-off of each one is worth the stumbling blocks (is HM2 worth the extra hassle? Sometimes yes, sometimes no) as well as give the module maintainers useful feedback on what they need to work on.

DragoonBoots’s picture

Status: Needs work » Postponed (maintainer needs more info)

I do have a lot of homework today, but I'll fix those problems you mentioned as soon as I can.

Crell’s picture

No worries. Homework takes priority. :-)

DragoonBoots’s picture

I'm working on it now. I did just send Matt Koglin, the Druplet maintainer, a message to see if he has a release plan; For now, I'll just cut the sentence short at "Druplet seems very stable."

DragoonBoots’s picture

Do you want me to post the review now or wait until I get a response regarding Druplet's release status?

aclight’s picture

Status: Postponed (maintainer needs more info) » Needs work

Go ahead and post it now. That way, if we get a chance to review it now things might move a little faster.

BTW, we usually use the needs more info status for issues where someone reports a bug that can't be reproduced. In this case, we should go between code needs work and code needs review.

DragoonBoots’s picture

Status: Needs work » Postponed (maintainer needs more info)
StatusFileSize
new85.91 KB

This is the review, sans Druplet release plan.

DragoonBoots’s picture

I just wanted to let you all know - I haven't gotten an e-mail back from Matt, so the review as last posted is what I (personally) considering "latest version pending review".

DragoonBoots’s picture

I got the message. I'll upload the review with the release plan in it soon.

DragoonBoots’s picture

StatusFileSize
new86.01 KB
aclight’s picture

Status: Postponed (maintainer needs more info) » Needs work

A few typos/corrections need to be made:

1.) "administration of [m]any different sites a[t] once"

2.) "and saving [disk]Disk space"

3.) "The Multisite Manager tool is easily the best choice when managing multiple Drupal-powered website[s]."

The following quote is from Crell's review above (#18). You have touched on a few of these concerns, but I don't feel that you've addressed them fully. After reading your report, I still don't have a good sense as to why you say that the Multisite Manager module is the best choice of the three, and I don't have a good sense of which module would be best for my site.

- So how does Druplet actually work? It uses installation profiles, but what does it do with them? How does one create a new site? Is there a way to secure it in production? A multi-site manager that can't be used in production is not super useful. :-)

- For HM2, what "things" need to be checked out, and what's so complicated about svn? :-) Is the documentation for HM2 lacking?

- For MM, you say it uses the same "create content song and dance" as Druplet, but you don't say what that is in either case.

I'd like to see a lot more detail on each option. So far it looks like you're presenting the conclusion for each (Druplet is easy but insecure, Hostmaster2 is hard, Multisite Manager is easy and secure usually), but not any of the reasoning behind your conclusion. That reasoning is important, as it helps people evaluate if the trade-off of each one is worth the stumbling blocks (is HM2 worth the extra hassle? Sometimes yes, sometimes no) as well as give the module maintainers useful feedback on what they need to work on.

DragoonBoots’s picture

Status: Needs work » Postponed (maintainer needs more info)

I'll get this done as soon as I can.

DragoonBoots’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new118.34 KB

How's this?

aclight’s picture

If it's possible, can you also convert this to a .pdf and upload that when you upload new versions. I don't have open office installed on several of my systems, so that limits my capability to review this.

DragoonBoots’s picture

StatusFileSize
new144.71 KB

I love you OpenOffice.org PDF export feature :-)

aclight’s picture

Status: Needs review » Needs work

You've got a typo here: "Currently, it is not [computable] with Drupal 6."

Should be compatible.

If you fix this typo and upload your corrected document, I think we can give you credit for the task so that if you want to claim another before the deadline to claim tasks you can.

DragoonBoots’s picture

Status: Needs work » Needs review
StatusFileSize
new144.71 KB
new118.33 KB

It's fixed.

aclight’s picture

Status: Needs review » Reviewed & tested by the community

Ok, looks good. I'll give you credit for the google task.

adrian’s picture

HM2 was not ready for public consumption at the time this was made.
it's improved a lot, but is still in development.

add1sun’s picture

Component: User Guide » New documentation
Status: Reviewed & tested by the community » Closed (fixed)

Hrm, so this is rather outdated information now so, while interesting, it isn't really a good thing to publish at this point. I'm going to go ahead and close this.