? INSTALL-documentation-addition-and-cleanup.patch Index: INSTALL.txt =================================================================== RCS file: /cvs/drupal/drupal/INSTALL.txt,v retrieving revision 1.87 diff -u -p -r1.87 INSTALL.txt --- INSTALL.txt 1 Jan 2011 22:41:24 -0000 1.87 +++ INSTALL.txt 27 Jan 2011 21:18:46 -0000 @@ -10,7 +10,6 @@ CONTENTS OF THIS FILE * Multisite configuration * More information - REQUIREMENTS AND NOTES ---------------------- @@ -37,13 +36,12 @@ Note that all directories mentioned in t directory of your Drupal installation, and commands are meant to be run from this directory (except for the initial commands that create that directory). - OPTIONAL SERVER REQUIREMENTS ---------------------------- - If you want to use Drupal's "Clean URLs" feature on an Apache web server, you will need the mod_rewrite module and the ability to use local .htaccess - files. For Clean URLs support on IIS, see "Using Clean URLs with IIS" + files. For Clean URLs support on IIS, see "Clean URLs with IIS" (http://drupal.org/node/3854) in the Drupal handbook. - If you plan to use XML-based services such as RSS aggregation, you will need @@ -60,17 +58,18 @@ OPTIONAL SERVER REQUIREMENTS configuration allows the web server to initiate outbound connections. Most web hosting setups allow this. - INSTALLATION ------------ 1. Download and extract Drupal. You can obtain the latest Drupal release from http://drupal.org -- the files - are in .tar.gz format and can be extracted using most compression tools. + are in .tar.gz or .zip format and can be extracted using most compression + tools. To download and extract the files, on a typical Unix/Linux command line, use - the following commands (assuming you want version x.y of Drupal): + the following commands (assuming you want version x.y of Drupal in .tar.gz + format): wget http://drupal.org/files/projects/drupal-x.y.tar.gz tar -zxvf drupal-x.y.tar.gz @@ -89,7 +88,7 @@ INSTALLATION initially: - Download a translation file for the correct Drupal version and language - from the translation server: http://localize.drupal.org/download + from the translation server: http://localize.drupal.org/translate/downloads - Place the file into your installation profile's translations directory. For instance, if you are using the Standard install profile, @@ -299,7 +298,6 @@ INSTALLATION scripts/ directory. (Note that these scripts must be customized like the above example, to add your site-specific cron key and domain name.) - BUILDING AND CUSTOMIZING YOUR SITE ---------------------------------- @@ -317,12 +315,11 @@ multisite installation, you can also pla site-specific directories -- see the Multisite Configuration section, below. Never edit Drupal's core modules and themes; instead, use the hooks available in -the Drupal API. To modify the behavior of Drupal, develope a module as described +the Drupal API. To modify the behavior of Drupal, develop a module as described at http://drupal.org/developing/modules. To modify the look of Drupal, create a subtheme as described at http://drupal.org/node/225125, or a completely new theme as described at http://drupal.org/documentation/theme - MULTISITE CONFIGURATION ----------------------- @@ -332,16 +329,15 @@ its own individual configuration. Additional site configurations are created in subdirectories within the 'sites' directory. Each subdirectory must have a 'settings.php' file, which specifies the configuration settings. The easiest way to create additional sites is to -copy the 'default' directory and modify the 'settings.php' file as -appropriate. The new directory name is constructed from the site's URL. The -configuration for www.example.com could be in 'sites/example.com/settings.php' -(note that 'www.' should be omitted if users can access your site at -http://example.com/). +copy the 'default' directory and modify the 'settings.php' file as appropriate. +The new directory name is constructed from the site's URL. The configuration for +www.example.com could be in 'sites/example.com/settings.php' (note that 'www.' +should be omitted if users can access your site at http://example.com/). Sites do not have to have a different domain. You can also use subdomains and -subdirectories for Drupal sites. For example, example.com, sub.example.com, -and sub.example.com/site3 can all be defined as independent Drupal sites. The -setup for a configuration such as this would look like the following: +subdirectories for Drupal sites. For example, example.com, sub.example.com, and +sub.example.com/site3 can all be defined as independent Drupal sites. The setup +for a configuration such as this would look like the following: sites/default/settings.php sites/example.com/settings.php @@ -384,15 +380,14 @@ settings, consult http://drupal.org/gett For more information on configuring Drupal's file system path in a multisite configuration, see step 6 above. - MORE INFORMATION ---------------- - For additional documentation, see the online Drupal handbook: - http://drupal.org/handbook + http://drupal.org/documentation -- For a list of security announcements, see the "Security announcements" page - at http://drupal.org/security (available as an RSS feed). This page also +- For a list of security announcements, see the "Security advisories" page at + http://drupal.org/security (available as an RSS feed). This page also describes how to subscribe to these announcements via e-mail. - For information about the Drupal security process, or to find out how to