multisite

Hello everyone,

For a while I've been developing a system which allows a Drupal website to act as an authentication server and allow client websites to be connected to it. Once you register an account on one of the websites in the network you can use those credentials to gain access to any other website there.

I am writing this post because:
- We (Adulmec) are going to open source it so it makes sense to see if what we've done is of interest to you.
- I am not sure that some of our decisions are right and there might be better approaches which I did not see.

I am currently running a multisite installation with Drupal 6.13 on Lighttpd 1.4.19 and facing issues when creating Drupal sites in subdirectories.
After reading through countles posts here on the drupal sites, as well on lighttpd I am close to converting back to Apache as I can't get this to work.
The drupal directory structure looks like this

Drupal root: /home/www/drupal/sites

+sites
|______all
|______default
|______domain.com
|______blogs.domain.com
|______blogs.domain.com.blog1
|______blogs.domain.com.blog2

Goodmorning. We have some problems getting multisite to run on different urls. By different urls I mean

domain.com/city/project1
domain.com/city/project4
domain.com/anothercity/project2
domain.com/yetanothercity/project3

It's a single codebase, single database multisite install. Is it possible to do this? If so, what different configuration's do we need to think of?

I've suggested creating the different folders like
domain.com.cityname.projectname
etc

HI there

there is little performance issues if we have all modules at same installation. basically I have a site social, and i like to offer many facilities to users, but if i install many modules on same installation it impacts the performance, so i decided to user multisite,

for e.g.,

songs : songs.example.com
videos : videos.example.com
groups: groups.example.com
blogs: blogs.example.com

something like that.

I'm currently doing a proof of concept for Drupal as our Enterprise wide CMS. Our current site is http://www.cdha.nshealth.ca/. The current site is in a complete mess, and lacks and any decent functionality. We currently have 160+ sections on this site with approximately 200 contributors managing their own content.

I've used Drupal for 2 weeks. I read many articles about multisite but there is no article can make me satisfied.

I want to have a system:
- Multisite: a main site (mainsite.com) and many subsites (sub1.mainsite.com, sub2.mainsite.com, ...)
- All sites use one core Drupal
- Single sign on, user can sign in every sites to use resources (i'm want to use LDAP to manage users)
- Shared vocabulary and terms
- There are some contents appears all sites (but they can be only posted once)
- Using one or more database
- user's permission is different from sites

Hi,

Does anyone have any knowledge/experience of using the multisite module. I am looking to create my second drupal site and am considering using the multisite module. Is this a good idea? All thoughts welcome.

thks,
nolan.

One thing I can't get my head around is how to set up the folder structure on my local development environment, then on a live host (eg sandbox stuff, site testing, demos etc).

Let's imagine on my local machine, with all the right virtual hosts set up as http://site1, http://site2, http://site3 etc, my drupal/sites folder would contain: drupal/sites/all, drupal/sites/default, drupal/sites/site1, drupal/sites/site2, drupal/sites/site3...

<

blockquote>EDIT: The below applies to Drush version 2. Drush 3's site aliasing makes life a lot easier, as there's a built-in alias which means "all sites." So running a command across all sites in a multisite is as easy as:

You'll be interactively prompted on whether you really want to run the command on all your sites; to automatically skip this (for non-interactive cron run scripts, for example), add a -y flag to the command. For example, you can create a root crontab entry which looks like:

Hi there,

I'm attempting my first multi-site, single codebase drupal 6 installation using prefixed tables to share common data.

Background

Looking from the outside, I think the best way to explain my reasoning for this configuration is going to be module management, and to ease the development of the core facilities the site(s) will offer.

I'm attempting to split the rather large modules apart so I end up with subdomains offering the features the users require, here is the basic layout.

<

ol>