Posted by scotthoff on October 18, 2010 at 6:15pm
I have never done a drupal multi-site. I have an EXISTING site that works but is not on drupal. It consists of static files.
It seems that in the drupal multi site set up, I create a sub directory in sites such as mydomain.com. When I navigate there from mydomain.com, the drupal install realizes that I want to use the specified database and renders the site correctly? Is this correct?
However, it seems that I can't do or test this b/c mydomain.com is already in use by a live site. How do I get around this?
Comments
Where do you want to put the Drupal site?
Do you want the existing static site to sit side-by-side with the Drupal site? Then you're better off using virtual host and different folders...
Or, do you want to move the static site to Drupal? If so, you should use a test domain, even localhost, and build your site in Drupal first, then publish to the live environment.
I hope I'm understanding your question right...
Yes you can
Yes, you have realized that you can only have one URL pointing at a particular site. How else can apache and then drupal figure out how to satisfy the request.
But you can configure any mixture of the following today on a multisite and also change them later when you are ready to go live.
This requires some some drupal configuration and some apache configuration.
mydomain.com -> your existing static site
mydomain.com/site1 -> drupal site
site2.mydomain.com -> drupal site
myotherdomain.com -> drupal site
dns and apache set up?
in order to have the drupal site served up when a domain is requested, there are two things that need to happen:
1) DNS needs to resolve the domain to the box running drupal
2) apache (or other webserver) on that box needs to route requests at that domain to the drupal directory
so if your drupal install is on your live, hosted, environment, you have the first one done.
now you need apache to send requests for example.com to drupal, and drupal should have an sites/example.com directory to handle the request.
dunno if this helps. hope it does. :)
dns trouble
Ok. Thanks very much for the input thus far. I am very comfortable with php and web design but when I get to DNS and apache, I am challenged.
Looks like firefox and IE won't let go of old DNS. We opened chrome and it took us to the page to run the install. A few hours later this might be the fix. Backing up server before the install. We shall see!
It was 100% a DNS issue. We
It was 100% a DNS issue. We figured out how to trick our internal network to think that it was coming from the domain without changing it to the public.
Thank goodness for my networking guy.
Thank you to everyone who voiced a response. This was, at least for me, pretty challenging.
Is there anyone can help me
Is there anyone can help me out of multisite. I have tried but no luck.
I created subsites like /sites/site1.mydomain.com and created symlink but with no luck. if anyone knows better solution please I need instruction.
Many thanks with your help.
drupal docs, apache, dns
@afaaro
1) have you read http://drupal.org/getting-started/6/install/multi-site?
2) do you have an apache vhost set up for each of your multi-sites?
3) do you have either:
a) DNS set up to resolve the domains to the drupal install or
b) set up your hosts file to do so locally
let us know!
Hello sir, I also got
Hello sir,
I also got confused about the symlink. It turns out, I didn't need that at all.
The bare essentials are:
This worked for me but was very confusing to figure out. perhaps I don't read directions well!
multi-site
The way I did it is by the following structure
/var/www/drupal (is a link to the latest drupal version for instance drupal-6.1.9), makes it really easy to upgrade, just download the newest version of drupal and repoint /var/www/drupal to the newest download
I moved /var/www/drupal/sites out of the drupal directory so its located in /var/www/sites and under sites I have all of my different domain like www.ceveryday.com, www.myhealthcurve.com, etc.
Under each domain directory (not needed to call it www.ceveryday.com but makes it easy) you have www.ceveryday.com/files www.ceveryday.com/modules www.ceveryday.com/themes www.ceveryday.com/all/libraries (used for wsysiwyg editor library files)
And that is it; it wasn't easy at first because I use to have a new install of Drupal for every domain but the multi-site setup now works excellent. I have now build a template server and I'm selling a full VPS Ubuntu server with 2GB RAM and 40GB for 135ドル per month, includes NginX, MySQL, APC, MemCache, Dovecote, Postfix, ProcMail, Webmin, SSH, and Apache (disabled because NginX is better) and its behind a firewall. It has the ability to spin up to 16GB of RAM.
The whole VPS configuration is easy to maintain and its setup for multi-site and you can easily add domains and sub-domains with a quick little file that I have created. I don't have a web page for it yet but if you are interested let me know by sending an email to cwittusen@myhealthcurve.com and I can spin up a new server within 8 hours and its ready to go to town for you with everything already configured.
Regards,
Chris
Regards,
Chris W
@nick johnson I have no
@nick johnson
I have no access to these application, I am in a normal hosting. Is there anything else i can do with it
Many thanks
I think this was confusing
I think this was confusing enough with total control over the server. I might either switch hosting as suggested or purchase some more open hosting as a test bed. once you master the mechanics, you could try taking it back to this "normal" hosting.
Re: @nick johnson I have no
If you mean shared hosting, then you are likely to have problems with multi-site. I'd recommend switching to a VPS, using someone like slicehost or linode.