Posted by kpastore on September 30, 2008 at 4:39pm
I am running Drupal 5.10 and have access to cPanel and the root server, but have not implemented this setup before. My ideal situation is to have one table for users and separate tables for content. If anyone feels up to it, I would be extremely grateful for a tutorial, walkthrough, or advice. I have read as much info as I can find on this, but I think I just need someone to be there this first time through, as I am just not that familiar with the database side of drupal. Thanks in advance!
Comments
Clarify...
So to clarify, you want to have at least 2 sites served by the same Drupal install and you want the two sites to share the "users" table. Right?
also...
Do you have the multisite up and running already? If no, then I can walk you through that. We can do it on skype and see who else wants to listen in.
- dv
I have a single drupal
I have a single drupal installation set up, on a single db. I have also created the sub-folders under 'sites' where I now have - /sites/all/, /sites/default/, and /sites/domain.com.subsite/. That is the extent of it at this point. From what I understand, I will need to change the settings.php file of the subsite folder, but am confused as to what comes next. I've read about symlinks, changing the db string, etc... but there is just no clear, concise info out there.
And yes, I need two sites (at this time), though more will likely follow. There could be as many as 50 (one for each state) by the time it is all said and done, and I would need to have them all share the user table. Does Drupal allow for more sites to be added to the multisite installation over time, or do all of these need to be set up at the same time?
I want in
I tried to do one of these over the weekend and just gave up. I was providing Trevon with space to start doing his own tweaking which now is a full (second) install at trevonhines.tanishaharris.com so I would love to learn the ins and outs as well. Kevin thanks for posting.
~T
Here's the scoop.
You can take any standard Drupal installation and make it a multisite at any time.
In this example we will take drupalindy.com and create a second site called events.drupalindy.com. While I chose a subdomain I could justs as easily have chosen drupalindyevents.com. It would make no difference.
1] go to www/sites and create a folder with the full name of the second site.
for this example that is events.drupalindy.com
so the full path is www/sites/events.drupalindy.com
2] copy your settings.php file from sites/default
some people place the settings.php in the sites/all wherever it is get a copy of it over to www/sites/events.drupalindy.com
3] Use your MySQL tool to create a new database, a new user, and a new password.
4] Edit your new settings.php to reflect the new datavase, user, and password. Line 92 in Drupal6. The comments above line 92 explain exactly how to edit the database settings.
5] Here's the fun part. We need the registration of this domain to point to our Drupal install.
In the case of Drupalindy.com I use godaddy and I have the NS1 and NS2 settings pointed to godaddy so that I can have Total DNS Control. That is actually the name of their DNS service, TDC. So I go into the records and create a new "A Record" with the host of "events" and the I.P. of my server.
If you don't know the IP of your server then:
a] Run a command line "ping drupalindy.com" and see the results. Hit CTRL-C to stop the ping.
b] You can also goto whois.sc/drupalindy.com and look under server-data. obviously you will be using YOUR domain and not the drupalindy.com in this example
If we were using a whole separate domain like drupalindyevents.com then we would do this.
a] register that domain and point the DNS to the registrar so that we can use the "A Records"
b] create a record for "@" to point to the IP of our Drupal install
c] Create a "www" records to point to "@" [[[users can get our site with OR without www and google only sees ONE SITE.
6] Wait for the DNS servers around the world to catch up to your lightening speed changes of DNS records..
7] Now that the events.drupalindy.com us resolving to the server with our Drupal install we need to install Drupal!
Yep... We're going to goto events.drupalindy.com/install.php or with the other example drupalindyevents.com/inostall.php
What will happens is that drupals install process will take place using the data of the settings.php file that we created inside the new site folder.
8 OH YAH!!! goto your sites/events.drupalindy.com folder and create a folder named "files" and set the permissions to 777
That will get you to a 2nd site on top of one install of Drupal.
When that's done, we'll talk about sharing the user table so that any user created by one site is visible to all sites.
Shoot me any questions any of you may have.
- DV
Awesome! I will be giving
Awesome! I will be giving this a shot tomorrow, as I have an event this evening. Thanks for taking the time to lay all of this out. It seems this may be the best I have seen it explained so far. I'll let you know how it goes.
Thanks again!