Correct, just a separate database and a separate "files" directory for uploading of images, documents etc.

http://www2.evergreen.edu/dave http://www2.evergreen.edu/itch http://www2.evergreen.edu/ITTrainingRoom

Are three sites hosted from the instance of drupal (same php, themes, modules, etc) against different databases. I'm running on linux, apache, mysql. Technically each of these directories are just symbolic links to the one drupal code base.

To make it really easy to manage, I've developed some shell scripts to create sites by cloning mysql databases, making a few symbolic links, directories, and building a custom settings.php file.

-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Fran Fabrizio Sent: Friday, June 30, 2006 4:49 AM To: support@drupal.org Subject: Re: [support] Providing ownerships of a subset of the siteto user/group

By separate database, do you mean separate instance of drupal? Or does it use all the same PHP/CSS/themes/etc... install but just have a diff. mysql db?

Metzler, David wrote:

The way we are using this is that we actually create a separate database for each site section. The look and feel is controlled centrally as all sites have the same "theme" applied, but each site has its own separate database. Then you establish different roles for

each site, but all are

using the same "code base".

You can also set a similar thing up in the same database, but you need

to do the multi-site install. I find that to be more complicated than

it's worth, but others find it quite valuable.

David Metzler The Evergreen State College

-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Fran Fabrizio Sent: Thursday, June 29, 2006 3:45 PM To: support@drupal.org Subject: [support] Providing ownerships of a subset of the site to user/group

We are investigating Drupal for our department web site. Right now there is a person or group of persons responsible for each part of the

site.

When we convert to Drupal, what's the easiest way to give a user or role permission to "own" (i.e. the only ones who can edit that section) a set of pages without giving them permission to edit all pages or to publish pages outside of that area? Is there a module that

is set up to handle this sort of "sandbox" model?

Concrete example (we are a department in a university). One of our faculty members is in charge of all the pages dealing with the graduate program. In our current site, this translates to all pages in

the /graduate area. He owns all of the files in that folder, and can only publish new content to that folder. Another person is in charge of the undergraduate program (/undergrad), a third person is in charge

of the continuing education program (/conted), and so on.

How best to model this in Drupal? Is this something that Drupal is well-suited to handle?

Thanks!

-- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama at Birmingham http://www.cis.uab.edu/ 205.934.0653 -- [ Drupal support list | http://lists.drupal.org/ ]

-- [ Drupal support list | http://lists.drupal.org/ ]