So here's the deal: I want to install a multi-site installation of Drupal, without going live right away. Currently my situation is this:
http://www.talent71.com/drupal/ - This is the folder I installed Drupal in. When finished, I will direct talent71.com to go directly to this folder.
http://www.talent71.com/drupal/sites/freshtunesfinland.com - This is the folder I created for the multi-site installation of my second site. When finished, I will direct freshtunesfinland.com to go directly to the drupal-root.
http://www.talent71.com - This is the main site, which is live right now
http://www.freshtunesfinland.com - This is the second site, which is live right now
Both of my sites are live right now, so I can't make freshtunesfinland.com point to the drupal-root right now, until I've managed to theme it, create the content, etc. The problem I have is this:
If I try to navigate to http://www.talent71.com/drupal/sites/freshtunesfinland.com I get a "403 Forbidden" -error. How do I proceed??
Comments
=-=
I'd build it on a local machine which will keep search spiders away from it until it is ready to go live.
another option, is to build in a subdomain of either domain name, though I'd still do the previous method.
Unfortunately building on a
Unfortunately building on a local machine is not an option, since there are different people developing the site from around the country.
But how would the subdomain-option go? I'd make a drupal.freshtunesfinland.com and make that point to talent71.com/drupal? Would Drupal recocgnize it as the sites/freshtunesfinland.com -site? Won't that put my databases in a fuzzy?
=-=
after it's built I'd move it to the root. Drupal is modular in that way so long as you use relative urls.
the sites folder would have to reflect the subdomain not the full domain.
I'd still use a local development machine, with a versioning control system where the files can be checked out. ie: git, svn, bzr any of them should work for multiple developers working on the same site.
But if I'd rename the
But if I'd rename the "sites/freshtunesfinland.com" folder to "sites/drupal.freshtunesfinland.com" and build the site on drupal.freshtunesfinland.com, wouldn't the renaming back to "sites/freshtunesfinland.com" screw up the databases / something else?
i think yes
90% you'r right
=-
Than you are are only 10% right.
it's no different than building it in a localhost or another server and moving it to a new host.
switching the folder won't matter after the fact, clear the cache tables in the database. if the DNS resoloves and points to the correct folder ie: where index.php lives in drupal, it will resolve to the correct folder. db connection can also be changed after the fact if you wanted to. Export the DB, import into new db, edit settings.php to point to new name and your done.
if you just absolute urls in your building then yea, you will likely code yourself into a corner, but you would do that no matter where you built the site first.