CiviCRM Community Forums (archive)

A discussion of the ramifications of the installation domain and folder structures would be helpful.

Here is how we are currently running:

Domains:
= = = = =

domain1.org - public website different CMS, nothing to do with Drupal or CiviCRM
domain1.com - administrative backend, various applications including drupal to launch CiviCRM (currently 1.9)

domaintest.com - testing CiviCRM 3.1.2

domain2.org - another installation of Drupal / CiviCRM for an other activist group

domain3.org - considering another Drupal / CiviCRM installation, perhaps time to review the multi-site ??

Folder Structures
= = = = = = = =

domain1.com/drupal
Even though we've run drupal and civicrm for a couple of years, only use drupal to launch civicrm.  If browse to the document root, the visitor is forwarded from the .com to the public .org website.  Don't know much of anything about Drupal and only use to launch CiviCRM, lately been starting to wonder if Drupal could do other useful tasks.   One item that is perplexing is the folder structure.  It is nice to have the document root tidy with each application in a separate sub-folder.  Also, when extracting drupal on the server from the compressed file, it naturally goes to a folder "drupal and the version" (we rename folder to just "drupal").  Seems like to use Drupal as a front-end, would be better to run at the document root, but then messy document root directory.  What would be nice would be to be able to install drupal in the drupal folder and move one index..php up to the root where the index file is able to know where to find things, but I guess Drupal does not work that way.

What domain and folder structures are others using?