Multisite question(s)
Hello all,
I'd like to set up my first multi-site for two very similar sites on a LAMP configuration, using a Godaddy shared hosting server.
Here's what I've done, in the approximate order:
1) I've installed one instance of Drupal 5.7, complete with one database
2) created a sites/ directory according to this original set of instructions. (note: of all the multi-site instructions, this seemed to be the easiest to understand)
3) I copied the settings.php file from the sites/default folder to each of the two new site's folders
4) I understand this 'copy' of settings.php must be changed so the database knows where to look. (Right?)
5) I've modified my settings.php file, for each /site/name.com with the
db_url = 'mysql://username:password@localhost/databasename';According to this original set of instructions, I am to
Configure Drupal site settings to specify 'File System Directory' of 'sites/example.com/files' instead of the default 'files'.
...I'm not exactly sure what this is about either. Is this the same as #5 above?
I have a few more questions, but if this sounds right (or wrong), I'd appreciate any feedback before asking the other questions.
Thanks to all,
kwg

Have u....
....is it possible to ask ur webhost to configure wildcard DNS for your account...then Domain Access module can be used to setup multisites on a single drupal installation n share database and users on all the domains or subdomains.Check out the Domain acces module and see if its th eone you actually need at drupal.org/project/domain
1, 2, 3) Fine. 4) Almost.
1, 2, 3) Fine.
4) Almost. The copy will be changed by Drupal's installation program, so that the site knows where its database is.
5) No. The copies must be unmodified or else Drupal's installation program won't install your new sites.
I guess you have also created databases for your news sites? Or you are going to use the same database with different prefixes?
What does this mean: In Drupal's
admin/settings/file-systempage, if your files directory is justfilesthen this directory will be created under Drupal. So, if you don't change it, all your sites will put their files at the same place.So, you need to make it different for each site. Some people like to make it
sites/www.site1.com/filesother people preferfiles/site1. It is fine as long as it is a different directory for each site.You are halfway there. The other half is to make all your domain names point to where Drupal is installed.
Thank you both.
Thank you both.
Cog.Rusty,
Let me get this stright - I do not need to change the settings.php text for each new sites/example.com directory? ...so I should go back, and copy/paste original 'defualt' settings.php into each /sites/example.com directory?
As for databases, I only have one DB set up, for the default installation. The two sites will be quite similar, and not overly compilcated. I dont know if its better to have same DB (with prefixes) or seperate DBs. Suggestions?
Thank you,
Kelly
Yes. In Drupal 5, when
Yes. In Drupal 5, when running the installation script for a site, the corresponding settings.php file must be unmodified (a fresh copy of the original) or else the installation script will tell you that the site is already installed and will proceed to the site (giving you errors, of course).
About the databases, if you do not intend to make any complicated tricks mixing content from the two sites, then using two separate databases is probably better. For example it will be easier to move or to wipe out one of the sites, maybe slightly better performance, a buggy module which doesn't handle prefixes well won't cause any harm... But these may be far-fetched, not so important.
Thx! On to next questions...
Thank you.
I've copied/replaced the Default settings.php file into the two new sites' folders....they should be copies of the original.
The two sites are www.livevicariously.net and www.newmexicokayakinstruction.com. Currently, they both show the standard "welcome to your new Drupal site" as seen after the install script has been executed. I'm a bit confused, because aside from the orginal install (and orignal creation of the single DB) - how is it that both sites can have the 'welcome to your new Drupal site'? (I just reserved newmexicokayakinstruction.com yesterday! long after installing the original instance) Are they both being pointed to the original install? Seems like it. ...is there an additional 'install' step I must take to create individual DBs (or at least prefixes), SuperUser, etc?
This has been the mystery of the Multisite (for me) for a while. Typically, I upload Drupal to the server, go to domain.com, add the install.php script, and Drupal does its thing, then I build site as needed. At this point, its hard to tell one from the other.
Many thanks!
testing the waters...
I created a new superuser, and changed the site name from Drupal to New Mexico Kayak instrucion. Turns out, this changed the title for both sites. This is kinda what I expected would happen from using the same DB...just not sure how to correct it.
If you installed Drupal only
If you installed Drupal only once, probably the other domains are also showing you the same site. I can think of two possible reasons for this:
1. If the names of the directories under sites/ are not correct, Drupal finds no match for the requested site and sends you always to sites/default.
The correct names for those directories are
sites/livevicariously.net
sites/newmexicokayakinstruction.com
2. If the settings.php file which you copied was not really a fresh unmodified one, but contained a $db_url with the database settings of the first site, then all sites will use the same database settings and will be practically identical.
If this is the case, get a new clean copy of the sites/default/settings.php file from the drupal-5.7.tar.gz package.
Then when you visit one of the new sites the installations script will start again.
Thanks Rusty, I think I got
Thanks Rusty,
I think I got it working now. Both sites are up. I uploade one module (admin menu) and it appeared on the modules page for both sites. I enabled it for one, but not the other, and it worked. I've now started with some more site specific stuff (site information, etc) and it appears to be working 'like a multi-site should' ;^)
Thanks again for your help!
kelly