I am sorry if this is a repeat, but I am having trouble finding information specific to my multisite setup.
- I am on a shared server, cpanel and shell access.
- I have drupal in a public_html/drupal6.
- All parked/sub domains point to this folder via symlinks, set up via shell access.
This all works great, and means that I can easily upgrade drupal by overriding this folder.
The hitch is this: my main domain also runs off of this drupal install. The only way I have been able to get this to work is to create an index.html file in public_html/ that redirects to "home" which is a symlink that points to drupal6 (index.html --> "home" --> drupal6). This means that all content in my main domain is at http://maindomain.com/home/.... I would really like to get rid of "home" and keep drupal in a subfolder.
Is there a way to do this? I feel like I am missing something obvious, but most multisite descriptions seem to assume that all drupal files are in the public_html or require modifying an apache file I don't have.
Thanks,
Maria
Comments
If your main domain can be
If your main domain can be altered to point to public_html/drupal instead of public_html, then you're golden. Then you can just use drupal/sites/default to hold your main site settings. Does your cpanel/host allow this?
two question, the first is
two question, the first is probably dumb:
how do you do this in cpanel? I never use it as I use ssh, and a redirect does not do what I want (I can redirect to the folder, but I don't want the url to read http://mysite.com/drupal6, just mysite.com).
If I do this, will it redirect all traffic to drupal? I have some dev and other sites that are non-drupal in public_html as well.
You may be able to configure
You may be able to configure your web server so that the Drupal directory is the web root, not the directory above it; at least for when your main site's domain name is used in the request. If not possible, then you may be able to just move your Drupal files directly into the web root directory instead of the "home" directory.
Also, you may also be able to configure your web server so that that Drupal directory is the web root by default for all domain names used to access the server, so no symlinking is necessary.
The Boise Drupal Guy!
*_*
I guess, your hosting provider will not allowed you to create/alter a .conf file that alter the way apache/any web server looks at your site. It it is, I want to change my host.
BeautifulMind
Have you set this up in your multisite setup?
Not sure if you've done this...
After you make the sym link for the subdomain, you need to create a folder under sites for each subdomain, in the form, subdomain.maindomain.com, and put a settings file in this folder. That's the only thing in the folder.
If you have images with your subdomain, set up the CCK FileField Path settings, File path: with a token of [site-name], and the first time you save the image, Drupal will create a directory with the site-name under the sites/default/files folder. Your images will be separate from the main domain's and from each subdomain's. Same with files.
Nothing needs to go outside of public_html nor have any apache files altered. That's why I chose Multisites rather than Domain Access since I'm on a shared host, and my setup is working well.
I need to talk with my server
I need to talk with my server about options. Right now, I have multiple subdomains running. The problem with pointing my entire webroot folder to the drupa folder is that I also have non-drupal sites running on my server, so my public_html/ needs to be accessible. All the drupal subdomains have a symlink pointing to the drupal6/ folder. It is just that I want my main domain pointing there as well. Right now, I have an index.php page in public_html which runs a script pointing to "home" which directs to drupal6/.
Having very similar problem
I'm also trying to setup a server that has legacy non-Drupal content to point its home/root to a site within a subfolder-based multisite Drupal instance ("home") sitting on it. I still want to serve the legacy content, preserving their current paths, as well as other (non-home) sites off of the multisite instance mentioned above.
Here's my dilemma: my service provider has given me access to add aliases and redirects (conf include files), but won't let me change the doc root (httpd.conf itself).
I successfully got this working on a test server by setting changing the docroot to the "home" instance. I used the default site (sites/default) to implement the main page and limited (<10) top-level folders that the user will see when hitting the main domain. Since the legacy content was also limited to roughly 10 top-level folders, I setup Alias directives to point to them on the true docroot (e.g. Alias /legacy_folder /full_path_to_true_docroot/legacy_folder). This allowed me to address the existing top-level folders and contents normally. Likewise, I used the Alias directives for the sites on the "home" and a separate Drupal instance.
Since I'm not unable to go that route, however, I've got an alternative however not sure how to execute it.
I want to see if there's a way to alias or redirect requests just to the root (^/$) to go directly to a home instance site set up as "example.com.home". Setup a rewrite that "tidies" all /home/* paths changing them back to /*. Then alias the home instance's top-level directories, so e.g. /aliased_top-level => /home/aliased_top-level - however maintaining the "clean" non-"home" path. Any ideas or alias/rewrite/redirect magic anyone can share?? Thanks in advance.
Have a look at Drupal's
Have a look at Drupal's .htaccess file (within your Drupal directory). Close to the bottom of .htaccess will be 2 methods for redirecting requests to your Drupal install.
The 1st way is to simply set the path to your Drupal root (i.e.: /public_html/drupal6 => yourD6site.com)
The 2nd way is to set your virtual web root, which to explain set-up here would be complicated.
Regardless, as long as your sites dir was set up correctly (i.e.: public_html/drupal6/sites/yourD6site.com/settings.php and public_html/drupal6/sites/yourOtherD6site.com/settings.php, etc.), you should be all set.
Good luck, hope this helps.
_rs