drush.ini 3.31 KB
Newer Older
Colan Schwartz's avatar
Colan Schwartz committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94
;
; Example of a drush php settings override file
;
; IMPORTANT:  Before following the instructions in
; this file, first check to see that the cli version
; of php is installed on your system.  (e.g. On
; debian systems, `sudo apt-get install php5-cli`.)
;
; Use this file in instances when your system is
; -not- configured to use separate php.ini files for
; webserver and cli use.  You can determine which
; php.ini file drush is using by running "drush status".
; If the php.ini file shown is your webserver ini
; file, then rename this file, example.drush.ini,
; to drush.ini and copy it to one of the following
; locations:
;
; 1. Drush installation folder
; 2. User's .drush folder (i.e. ~/.drush/drush.ini)
; 3. System wide configuration folder (i.e. /etc/drush/drush.ini)
;
; If the environment variable DRUSH_INI is defined,
; then the file it specified will be used as drush.ini.
;
;    export DRUSH_INI='/path/to/drush.ini'
;
; When in use, the variables defined in this file
; will override the setting values that appear in
; your php.ini file.  See the examples below for
; some values that may need to be set in order for
; drush to work.
;
; NOTE:  There is a certain amount of overhead
; required for each override, so drush.ini should
; only be used for a relatively small number
; of variables.  Comment out any variable that
; has the same value as the webserver php.ini
; to keep the size of the override list small.
;
; To fully specify the value of all php.ini variables,
; copy your webserver php.ini file to one of the
; locations mentioned above (e.g. /etc/drush/php.ini)
; and edit it to suit.  Alternately, you may use
; the environment variable PHP_INI to point at
; the file that Drush should use.
;
;    export PHP_INI='/path/to/php.ini'
;
; The options listed below are particularly relevant
; to drush.
;

;
; drush needs as much memory as Drupal in order
; to run; make the memory limit setting match
; what you have in your webserver's php.ini.
;
;memory_limit = 128M
; Actually, give it a bit more. Some batch processes, such as Search API
; indexing, aren't terribly memory-efficient. See
; https://www.drupal.org/node/1137734 for details.
memory_limit = 512M

;
; Show all errors and direct them to stderr
; when running drush.
;
error_reporting = E_ALL | E_NOTICE | E_STRICT
display_errors = stderr

;
; If your php.ini for your webserver is too
; restrictive, you can re-enable functionality
; for drush by adjusting values in this file.
;
; Here are some examples of settings that are
; sometimes set to restrictive values in a
; webserver's php.ini:
;
;safe_mode =
;open_basedir =
disable_functions =
;disable_classes =

;
; Workaround for:
; date(): It is not safe to rely on the system's timezone settings. You are
; *required* to use the date.timezone setting or thedate_default_timezone_set()
; function. In case you used any of those methods and you are still getting this
; warning, you most likely misspelled the timezone identifier. We selected the
; timezone 'UTC' for now, but please set date.timezone to select your timezone.
; sync.sql.inc:331
;
date.timezone = "America/Toronto"
95 96 97

; Allow drush commands to run for a while as the default timeout could be too
; short.  See https://www.drupal.org/node/587250#comment-3506436 for details.
98 99
; Make it unlimited explicitly even though this should be the CLI's default.
max_execution_time = 0