October 3, 2008 - 5:45pm
multisite
The multisite function of Drupal is awesome. To set it up, you need to name your folder after the website. Here is my folder structure.
Sites/all
Sites/default (this is my business account)
Sites/smileafricaministries.org
Sites/whereduck.com
You can keep going and going. If I wanted to add a subdomian, it follows the same idea.
Sites/coffee.whereduck.com
Sites/blog.whereduck.com
Sites/photos.whereduck.com
Each of the above websites would be a separate website.
David Richards
October 3, 2008 - 6:18pm
Hey David,
I think I
Hey David,
I think I understand the file structure. Does the ".com" have to be added? For instance I want to do a test site... so I made the folder.
Sites/testing
How would I then began to build the website "testing" and allow a user to log in and customize it?
I'm not to worried about doing the subdomains. But would rather do the sites/example.com.
If it's easier to explain/help you can contact me via iChat at TitusAV1611.
October 3, 2008 - 6:34pm
Drupal Multi-site
Hey JE_Illustration,
It should be noted there are several ways to setup a Drupal multi-site. I've been looking into this issue; wanting to achieve the same goal. One way is different tables prefixes. One database=several sites. This works, however it can lead to really big databases and I suspect security could be an issue.
If you're wanting an install which can handle the load of lots of sites, you will want a unique database for each site. Consider Drupal Multi-sight or the funky Multi-site with single codebase, different content databases, shared user database, shared sign-on.
Blessings!
-NP
October 3, 2008 - 7:33pm
Maybe you're getting a little ahead of yourself...
Hi Jason,
Before you worry about setting up a multi-site implementation you should probably get the base installation running. Things like adding content, creating accounts and roles (e.g., you already have one (UID=1), you should also create one for yourself with administrative privileges (SiteAdmin), one with what I call "Site Contributor" privileges, and any other general roles you anticipate).
You also probably want to start adding "common modules." Unfortunately, this is where experience pays dividends. One module you'll definately find useful is "Backup and Migrate". In order to be user friendly you'll probably want a WYSIWYG editor. You'll also want to load CCK, Views, CCK fields of various types, Contemplate, etc.
Now is the time to carefully name/place your "files" directory/folder. I recommend placing it at the "root level" (not the systems's root, but where you loaded Drupal) and incorporating the site's name in the name, e.g., I'm preparing a site for Some Foundation right now, so the files directory is /f-sf; it's short in case I have to type it and unique for any sites I may have on this server. Current (Drupal 6) practice seems to be to place the files folder in /sites//files. I don't have actual experience with D6 yet but I have reservations about doing this if the site is going to have several names (URLs) during its lifetime (on your development server, on a new version of Drupal, on the production site, etc.)
This post is getting a little long; since you know my number, give me a call.
One more thing, Acquia Drupal is available for download now. You don't have to be anyone special to use it. It comes with a lot of useful contributed modules already installed. If you're willing to be almost "bleeding edge" (or "The early Christians get the hungry lions") this is a pretty good start, although it lacks a WYSIWYG editor...
Curt
October 3, 2008 - 7:37pm
multisite cont.
My multisite setup is working perfectly with the *.com folder names. This is on a hosted server and the apache redirects are taken care of for me.
I have been playing around with the multisite setup on my dev server. I will let you know what I learn about setting up the directories and the redirects.
David Richards
So I have Drupal installed and working find on my server. I set up bogus links just to see how it did, and they are there under "navigation".
But here is what I am wanting to do. I am wanting the main Drupal install to basically be for setting up someone's website. Then have them be able to log in and allow them to update context of their sites themselves.
What I have so far is a basic drupal install... and I created a folder in /sites called "testing" and I copied the settings.php into the folder from the basic install.
I'm basically wanting to do a multi site drupal.
What I'm wanting to do is create a user and allow that user to have access to their site I create for them.
Am I making sense? I've read over and over the stuff over at drupal.org and listened to some of the podcasts, but I'm just not getting it... Just trying to learn this stuff on my own, can't afford any of the tutorials or books.
Not sure if this would help but it's located at http://www.mthopebaptist.com/drupal-5.10/
Thanks!