![]() ![]() If you are running on Linux, you may find that you need Multiple Drush configuration files can provide theįlexibility of providing specific options in different site directories of a If you get tired of typing options all the time you can contain them in aĭrushrc.php file. If you are using php 5.3.x, you may also need toĪdd the following definitions to your php.ini file: magic_quotes_gpc = Off You should insure that safe_mode, open_basedir, disable_functions andĭisable_classes are empty. The PHP_OPTIONSĮnvironment variable can be used to specify individual options that shouldīe passed to php on the command line when Drush is executed.ĭrush requires a fairly unrestricted php environment to run in. Not in one of the standard locations described above. In the case of PHP_INI and DRUSH_INI, these environment variables specify theįull path to a php.ini or drush.ini file, should you wish to use one that is There are three options: export PHP_INI='/path/to/php.ini'Įxport PHP_OPTIONS='-d memory_limit="128M"' You may also use environment variables to control the php settings that Drush Then you may edit this fileĪnd change the settings described above without affecting the php enviornmentĪlternately, if you only want to override a few values, copy įrom the /examples folder into $HOME/.drush or the folder /etc/drush and edit The folder $HOME/.drush or the folder /etc/drush. Php.ini file exclusively for Drush by copying your web server's php.ini file to If Drush is using the same php.ini file as the web server, you can create a To see which php.ini file the webserver is using, use the phpinfo() function in To see which php.ini file Drush is using, run: $ drush status Work with as the web server is otherwise, Drupal might run out of memory when Make sure that Drush's php.ini is given as much memory to Usually, php is configured to use separate php.ini files for the web server and bashrc that is located in your home folder: export DRUSH_PHP='/path/to/php' Php defined by your shell, you can add an environment variable to your If you want to run Drush with a specific version of php, rather than the ![]() Depending on the version andĭistribution of your AMP stack, PHP might reside at: PathĪcquia Dev Desktop v1 (Mac). The PATH variable, using the method in 3.b above. Want to ensure that its php can be found by the command line by adding it to Users of other Apache distributions such as XAMPP, or Acquia's Dev Desktop v1 will Additional Configurations for Other amp Stacks: ![]() MAMP FOR MAC PHP 5.4 HOW TOSee CONFIGURING PHP.INI below for more details on how to Sudo ln -s /Applications/MAMP/tmp/mysql/mysql.sock /var/mysql/mysql.sockĪdditionally, you may need to adjust your php.ini settings before you can useĭrush successfully. If you have done this and are still getting a "no such file or directory" errorįrom PDO::_construct, try this: sudo mkdir /var/mysql Of PHP: export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php5/bin:$PATH" ![]() If you have MAMP v.1.84 or lower, this configuration will work for both versions If you use MAMP 3 (php 5.5.14 by default) and want to use php 5.5.x, add this line instead: export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php/php5.5.14/bin:$PATH" If you want to use php 5.4.x, add this line instead: export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php5.4/bin:$PATH" bash_profile: export PATH="/Applications/MAMP/Library/bin:/Applications/MAMP/bin/php5.3/bin:$PATH" If it does not already exist) a file called. Version selected in the MAMP application settings. Users of MAMP will need to manually specify in their PATH which version of phpĪnd MySQL to use in the command line interface. Usage-show and usage-send commands to more carefully send data. Stats are usually logged locally and sent whenever log file exceeds 50Kb.Īlternatively, one may disable automatic sending and instead use To automatically send usage data, please add the following to a. bashrc/.bash_profile/.profile would produce this prompt: ~/repos/drush the Drush development team by sending anonymized usage statistics. If is being sourced (ideally inīash_completion.d), you can use the supplied _drush_ps1() sh function toĪdd your current drush site (set with drush use to your PS1 Once configured, completion works for site aliases,Ĭommand names, shell aliases, global options, and command-specific options. If you didn't source it the step above, see top ofĭ file for instructions on adding completion for drushĬommands to your shell. bashrc (or equivalent): source /path/to/drush/examples/example.bashrc You may source this file directly into your shell by adding to Useful shell aliases that provides even tighter integration betweenĭrush and bash. See example.bashrc for instructions on how to add some ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |