PHP scripts are executed in one of two ways; through a web sever where the output is sent to a browser, or through the command-line interface. Main difference between the two methods is the format of new lines. Output to a browser requires the HTML line break <br /> while the output to a command-window requires \n. This page provides a basic introduction to PHP CLI (command line interface). Minimum requirementsIn order to run PHP CLI scripts two Uniform Server ZeroXI modules are required. A controller ZeroXI_controller_1_1_8.exe and one of the PHP modules for example ZeroXI_php_5_4_35.exe The above combination is fully portable with a footprint of 53MB if you wish this can be pruned down see section Reduce footprint. Command-windowRunning scripts via a command-line is performed using the CLI interpreter php.exe this program is located in folder C:\Zero_11\UniServerZ\core\php54 note UniController automatically tracks the installation and changes this path accordingly. In addition UniController sets several environment variables that are required for portability.
Note 1: You can clear the command-window by typing CLS PHP Command-line - run code directelyThe above demonstrates running PHP code directly using the CLI interpreter php.exe php.exe -n -r "print phpversion();" The interpreter program takes a number of parameters who’s function are follows:
Note: If your code contains quotes to avoid problems these must be escaped using a backslash for example: php -r "print \"test\n\n\";" //-Print test and two new lines \n Code examplesThe following provide examples that you can cut and past into the command-window:
CLI configuration fileWith one exception all above examples are forced not to use a configuration file by using the parameter –n. The last example does not use this parameter and prints the default configuration file loaded.
The current configuration of this file is specifically for Uniform Server you can use this file however do not make changes to the existing configuration. Note: The default configuration file used is dependent on the PHP version selected and will be one of the following:
User ConfigurationTo avoid issues at a later date it is probably wise to use your own configuration file for example my_cli.ini this can be a name of your own choice. Create this file by making a copy of php-cli.ini in the same folder and rename it my_cli.ini make changes to this file as required. To force the CLI interpreter php.exe to use a different configuration file use the parameter –c followed by the full or relative path to the configuration file my_cli.ini for example: php -c K:\UniServerZ\core\php54\my_cli.ini php -c core\php54\my_cli.ini A problem with the above paths they are not portable or PHP switch able. Moving folder UniServerZ to a different location the first will fail because of the path change. Switching the PHP version for example to php5.3.7 both fail because of the folder change php53. A solution is to use the environment variable PHP_SELECT as follows: php -c core\%PHP_SELECT%\my_cli.ini To confirm the file is being picked-up correctly by PHP type the following K:\UniServerZ>php -c core\%PHP_SELECT%\my_cli.ini -r "print(php_ini_loaded_file ());" K:\UniServerZ\core\php54\my_cli.ini K:\UniServerZ> Summary: php -c core\php53\my_cli.ini //Fixed PHP php -c core\php54\my_cli.ini //Fixed PHP php -c core\php55\my_cli.ini //Fixed PHP php -c core\php56\my_cli.ini //Fixed PHP php -c core\php70\my_cli.ini //Fixed PHP php -c core\%PHP_SELECT%\my_cli.ini //Switchable PHP Note: An alternative although not PHP switch-able is to locate the configuration file in the root folder UniServerZ with an appropriate name for example my_cli_53.ini, my_cli_54.ini, my_cli_55.ini, my_cli_56.ini or my_cli_70.iniThis reduces amount of typing and the files are fully portable, use the one that matches the PHP selected. php -c my_cli_53.ini php -c my_cli_54.ini php -c my_cli_55.ini php -c my_cli_56.ini php -c my_cli_70.ini Running PHP scripts
Reduce footprintAlthough the footprint is 52MB it contains a full version of PHP and some additional utilities. You can reduce this footprint as follows: A) If you are not using the Internationalization extension (php_intl.dll) you can delete the following: K:\UniServerZ\core\php54\extensions\php_intl.dll K:\UniServerZ\core\php54\icudt53.dll K:\UniServerZ\core\php54\icuin53.dll K:\UniServerZ\core\php54\icuio53.dll K:\UniServerZ\core\php54\icule53.dll K:\UniServerZ\core\php54\iculx53.dll K:\UniServerZ\core\php54\icutest53.dll K:\UniServerZ\core\php54\icutu53.dll K:\UniServerZ\core\php54\icuuc53.dll The above achieves a significant reduction of 24MB B) If you are not using the PHP mail function disable this in the configuration files php-cli.ini and my_cli.ini by commenting (add ; to beginning of line) the line as shown below: ;sendmail_path = "${US_ROOTF}/core/msmtp/msmtp.exe --file=${US_ROOTF}/core/msmtp/msmtprc.ini -t" Delete folder K:\UniServerZ\core\msmtp saves 2.89MB C) You can further reduce the footprint by deleting extensions and any corresponding dependency this is left to your discretion as to what is deleted. However check the following dependency information before deleting an extension and or its corresponding dependency dll:
--oOo--
|