By GavinC on

I have an already running site using d6.x. What i would like to do is to have a subdomain running using the same code base, but seperate dbase.

I have had a look through the site and tried the CPanel multisite setup but failed to get this to work. I have my main D6.x installed in the /home/[user]/public_html

Could anyone point me in the right direction as i can only find d4.x and d5.x multisite install guides

Thanks in advance.

Squidge

⋅ Categories: Drupal 6.x

Comments

GavinC’s picture

GavinC commented

Can anyone help?

sharique’s picture

sharique commented

Try Domain module.
-----
Sharique

Sharique Ahmed Farooqui

GavinC’s picture

GavinC commented

@Sharique:

Thank you for that, i'll give that a go.

JohnnyMoney’s picture

JohnnyMoney commented

I just did a multisite install using Drupal 6.x
The hardest part to find out was the symlink issue.

Details are:
main site: www.mysite.com

second site: magazine.mysite.com
***

Steps I followed, without going into detail as I suppose you know most of it:
1) Create the magazine.mysite.com folder inside settings folder of main site, and inside put a copy of settings.php having done changes for the separate database (plus also the cookiedomain parameter for fckeditor if you use it).

2) Create a php script (createsymlink.php) that contains:

symlink("./mysite", "./magazine");
print "Done";

3) Upload that php script to my server into the public_html folder

(note: the mysite and magazine folders are both inside the public_html folder)

4) Erase the magazine folder, which was created by system when I created the subdomain using cpanel.

5) Execute the php script:
http://www.mysite.com/createsymlink.php

This will create a new folder inside public_html. Inside you'll see it contains the same stuff as the mysite folder.

6) Another important thing is that, for my new site (magazine.mysite.com) I had to prepopulate the database with the basic tables that installing drupal 6.x fresh creates; I wasn't able to just do an install from the browser.

***

I think this is all.
Now I am wondering if multisite has much of an advantage. For example, if I want to update a module to a newer version, won't I have to disable the module in each and every one of the multisites inside the administer section anyway, and then re-enable , etc.?