Hi,
I have my server set up and running several drupal multisites and all works great and really pleased with it.
On the same server I host another website (basic html based) which I am replacing with a drupal site. However, until the drupal site is 100% I want the html website to remain live until I switch it to the drupal multisite.
I am wondering how I can create and test a multisite on my server so that people visiting www.myWebsite.com still only see the html website until the drupal is ready?
So basically, if I add a new drupal conf that re-directs users from www.Mywebsite.com to the drupal multisites installation can I then re-direct users to an html website. I dont mind moving the html website to a directory within the multisite?
Once I create the multisite users will only see the drupal installation pages or the pages I am playing around with and not the original html website because I will have updated the ServerAlias in my apache conf. (I know I could get it up and running on a different host but I would like to use the server that has the multisite on).
I am a bit nervous playing with my server and drupal conf files as it took such a long time or trial and error to get multisite up and running? (and I only know enough linux / apache conf etc to get by!). Adding new sites to the conf is not a problem....
I am sure there is an easy way to do this and I look forward to your reply(s).
Hope this makes sense!
Comments
I've always wondered about
I've always wondered about this.
It would be cool if you could specify a conf path in the query string or system variable allowing testing of multisites before going live.
It may be possible for you to
It may be possible for you to create a new subdomain at, say, test.example.com, and set your Drupal installation directory as the web root for that. Then you could test by using different sub-subdomains - foo.test.example.com, bar.test.example.com. You'll have to use symlinks in your site directory and/or rename the site directories when your Drupal site goes live, but it ought to work.
The Boise Drupal Guy!
Subdomains will work to a
Subdomains will work to a degree and may suit OP. Contributed modules like imagecache don't behave when the domain is not the same and maybe this is another issue. Creating zone files on a development server for each site's domain works well but is not ideal for many reasons not to mention painful. I can't imagine a perfect solution for this being simple. I am very interested in other developer's methods.
Contributed modules like
I haven't run into serious problems taking sites across domain names - nothing clearing the cache and using Pathologic judiciously can't fix - but I have experienced problems when the paths beyond the domains change; for example, moving a Drupal installation at http://example.com/foo to http://example.com/bar. But these can usually be solved by doing a find and replace on the {files} table of the database, changing occurrences of the old path to the new one.
The Boise Drupal Guy!