Drupal Site Provisioning

Using "dsa.umich.edu" as an example, the Drupal site ID would also be "dsa.umich.edu". If provisioning a site in a subdirectory, the Drupal site ID would be dsa.umich.edu.subdirectory. In the following instructions, replace "dsa.umich.edu" with the actual hostname for the site:

• Create MySQL database for site, using same name as the Drupal site ID. If a marketing site for DSA, you can use the existing dsa-marketing user and password for the new database.
• Create directory with same name as Drupal site ID, and create sub directories:
  /home/web/www/sites/dsa.umich.edu
  /home/web/www/sites/dsa.umich.edu/drupal-assets
  /home/web/www/sites/dsa.umich.edu/files
• Copy the template version of the "settings.php" file to the "drupal-assets" directory, then edit this file and change the database name and access credentials.
• Copy the template version of the Student Affairs sub theme to the "drupal-assets" directory, and edit the name (possibly "DSA") of the theme for files, directories and in the .info file.
• Add a symlink in the Drupal "sites" directory that points to the "drupal-assets" directory you created above, and is named with the Drupal site ID:
  cd /home/web/www/drupal7/sites
  ln -s ../../sites/dsa.umich.edu/drupal-assets dsa.umich.edu
• Edit the "sites.php" file (in the Drupal sites directory) and add an alias to the dev host name (if used). Forexample, if using dev3.dsa.umich.edu to point temporarily to dsa.umich.edu, you would add the line:
  $sites['dev3.dsa.umich.edu'] = 'dsa.umich.edu';
• Add a symlink in the Drupal "files" directory that points to the "files" directory for the site, and uses a short version of site name:
  cd /home/web/www/drupal7/files
  ln -s ../../sites/dsa.umich.edu/files dsa
• Configure Apache and SSL with any virtual host settings as needed.
• Go to dsa.umich.edu/install.php and complete the installation of Drupal as normal.
• After successful installation, choose to go to the administration page:
  • Immediately activate the "Core Administration System" under the category  "University of Michigan Student Affairs - Features". This will provide Cosign authentication and force SSL login.
  • Add Tech Services staff as users with the "administrator" role.
• Go to menu item Structure::Features and activate the following features first, in the following order:
  1. Core Editorial System
  2. Editorial System Default Permissions
  3. Editorial System Default Content & Layout
  4. Any additional Features needed (you can activate later also)
• Clean up! Some basic setup needs to be done manually (need to document this, or even better script it).
  • Activate themes:
    • "Student Affairs"
    • Sub theme created earlier (DSA in this example), and make it the default.
    • "Seven Foot"
    • Make "Seven Foot" the "Administration theme"
  • Go to menu item Structure::Blocks and remove blocks (except "system help" and "workbench information") from the themes, since these are handled by Contexts.
  • Create a home page (content type "Basic page") and assign URL "home". If there is no content, you can leave it blank, but the page itself is required.
  • Go to menu item "Configuration::Site Information" and set "Default front page" to "home" (the page you just created above).
• Tips to begin populating the site:
  • To begin creating articles, you will need to add at least one term in the "Topic" vocabulary.
  • The main menu in the left sidebar is a standard Drupal menu, and is not dynamic — add links to the "Main menu".