00001 <?php 00002 // $Id: 00003 00004 /* 00005 * Examples of valid drush_multi statements for a drushrc.php file. 00006 * Use this file to cut down on typing of options and avoid mistakes. 00007 * 00008 * Append this file to drushrc.php. drushrc.php should be in one of 00009 * five convenient places, listed below in order of precedence: 00010 * 00011 * 1. Drupal site folder (e.g sites/{default|example.com}/drushrc.php). 00012 * 2. Drupal installation root. 00013 * 3. In any location, as specified by the --config (-c) option. 00014 * 4. User's .drush folder (i.e. ~/.drush/drushrc.php). 00015 * 5. System wide configuration folder (e.g. /etc/drush/drushrc.php). 00016 * 6. Drush installation folder. 00017 * 00018 * If a configuration file is found in any of the above locations, it 00019 * will be loaded and merged with other configuration files in the 00020 * search list. 00021 * 00022 * IMPORTANT NOTE on configuration file loading: 00023 * 00024 * At its core, drush works by "bootstrapping" the Drupal environment 00025 * in very much the same way that is done during a normal page request 00026 * from the web server, so most drush commands run in the context 00027 * of a fully-initialized website. 00028 * 00029 * Configuration files are loaded in the reverse order they are 00030 * shown above. Configuration files #6 through #3 are loaded immediately; 00031 * the configuration file stored in the Drupal root is loaded 00032 * when Drupal is initialized, and the configuration file stored 00033 * in the site folder is loaded when the site is initialized. 00034 * 00035 * This load order means that in a multi-site environment, the 00036 * configuration file stored in the site folder will only be 00037 * available for commands that operate on that one particular 00038 * site. Additionally, there are some drush commands such as 00039 * pm-download do not bootstrap a drupal environment at all, 00040 * and therefore only have access to configuration files #6 - #3. 00041 * The drush commands 'rsync' and 'sql-sync' are special cases. 00042 * These commands will load the configuration file for the site 00043 * specified by the source parameter; however, they do not 00044 * load the configuration file for the site specified by the 00045 * destination parameter, nor do they load configuration files 00046 * for remote sites. 00047 */ 00048 00049 /** @todo Implement that multi-site works with "apache-user" option from commandline too */ 00050 // (APACHE_RUN_USER) Used to set permissions to the webserver user (multi-site) 00051 // for settings.php during the installation and for the files directory 00052 // $options['multi-apache-user'] = 'www-data'; 00053 00054 /** @todo Implement that multi-site works with "apache-group" option from commandline too */ 00055 // (APACHE_RUN_GROUP) Used to set permissions to the webserver group (multi-site) 00056 // for settings.php during the installation and for the files directory 00057 // $options['multi-apache-group'] = 'www-data'; 00058 00059 /** @todo Implement that multi-sql-dump works with option "multi-sql-dump-target" */ 00060 /** @todo Rename --target option to something else, target is used by drush itself */ 00061 // Target directory used for writing the result files to (multi-sql-dump) 00062 // $options['multi-sql-dump-target'] = '/path/where/to/store/the/sqldumps'; 00063 00064 /** @todo Implement that multi-sql-dump works with option "multi-sql-dump-bzip2" */ 00065 // Use bzip2 for the compression of the result files (multi-sql-dump) 00066 // $options['multi-sql-dump-bzip2'] = TRUE; 00067 00068 /** @todo Implement that multi-sql-dump works with option "multi-sql-dump-datetime" */ 00069 // Use datetime strings in result file names (multi-sql-dump) 00070 // $options['multi-sql-dump-datetime'] = TRUE; 00071 00072 /** @todo Implement that multi-site works with option "multi-site-create-directories */ 00073 // List of optional directories created within a site directory (multi-site) 00074 // $options['multi-site-create-directories'] = 'modules/patched,foo,foobar';
1.5.8